Cannot create empty releases without Milestone or InputFilePath

[kristho91]

As of today it seems it's only possible to create a new release if either Milestone or InputFilePath is specified.
It could be great if it was possible to create an empty release with neither of those parameters.

[gep13]

@kristho91 thanks for raising this issue. I am just going through a process of triaging some issues, to know what to bring into the next release. Can you help me understand what the use case is for this issue? Why would you need to create an empty release?

[AdmiringWorm]

@gep13 I can see one use case (for me at least).

When initially creating a library/application I typically don't really create a issue for it (until I have to), so being able to run GRM without the need for existing issues would be useful in these cases.

[gep13]

@AdmiringWorm what would GRM bring to the table though that wouldn't be provided by simply creating the release through the UI? Or is it just the ability to automate that process? Happy to add this in, I just don't see an immediate benefit.

[AdmiringWorm]

Or is it just the ability to automate that process?

This ^^ for me. No other benefit AFAIK

[AdmiringWorm]

In general though, I do believe that GRM should throw an error on empty releases, but maybe adding a --empty switch or something (which skips the entire gathering of issues step).

[AdmiringWorm]

Could also be beneficial when working on build scripts to see if all is working as it should (that grm can create the release).

[gep13]

@AdmiringWorm said...
Could also be beneficial when working on build scripts to see if all is working as it should (that grm can create the release).

That's true.