CLI Tool?

[release-drafter]

CLI Tool?

[ssbarnea]

I am really interested about a CLI solution one that could be very easy to run in two modes: draft where it would only report what it would change and one that applies the changes. Unless someone will address this I plan to re-implement release-drafter in python as a cli tool, keeping the same config file. (Python because my JS skills are very low). Another feature I am considering is to allow it to be usable with other systems, like GitLab, or whatever other projects may use.

[oleg-nenashev]

A simple CLI tool would be really great.
I am working on a wider adoption of Release Drafter in the Jenkins organization (dev list), and it would be great to have a way to diagnose patches locally. Also, such CLI tool could be used to setup continuous integration for Release Drafter config files in .github

[oleg-nenashev]

@Casz @toolmantim I am experimenting with that this weekend. Will submit a PR if I manage to produce something operational (requires JS study)

[toolmantim]

Great idea! Assuming we could get it working simply enough with Probot/octokit.

[toolmantim]

Would happily accept contributions for adding CLI commands to the NPM package.

[ssbarnea]

This is very important because this could be used tu run release-drafter from other CI systems. As long you have github credentials setup (hub login) and you know the repository org/name, you should be able to run it.

[oleg-nenashev]

I am still planning to do something in order to support changelog generation for arbitrary releases in GitHub actions. Now it supports inputs and outputs, and hence there is more justification to have a CLI tool (at least a container-based one)

[jetersen]

I had a comment in another PR that should also help with providing a CLI:

you than a release-drafter/cli project as well.

I been thinking about converting the project to typescript. Add lerna to manage release-drafter/core, release-drafter/action, release-drafter/probot

Using actions/typescript-action as a base for release-drafter/action
With this we could potentially not deprecate release-drafter/probot?

As to those using release-drafter/probot be it GitHub enterprise or not can continue using it.
I was even thinking about providing a release-drafter/probot-monitor that would use Github OAuth to provide access to logs for the repos they have "write/(maintainer?)" access to.

#358 (comment)

[ssbarnea]

Any chance to make this a reality because lack of this option prevents running on already made releases, something quite desirable for project that never had it. The suggestion about repushing tags is something that should not have even being considered, mainly due to security concerns. Tags should never be altered, that's it.