Optional empty commit on release

[szpak]

It is great that axion doesn't depend on a version kept in a file, but it can be harder to notice a release just browsing commits (as tags are treated separately). There is a releases/tags tab in a GitHub interface, but sometimes it would be desirable to have a commit.

For those cases there could be a switch (disabled by default) which would make an empty commit with a message about release first and then tag it (there could be required an additional switch to allow JGit to accept empty commit).

[adamdubiel]

Nice feature, i would probably go with some configurable message template (like "release: $tag") instead of empty commit.

[szpak]

Yes, I also thought about a message (nice to have it configurable), but I don't know what files could be modified and because of that it wrote "an empty commit".

[adamdubiel]

Ah, i see. There is no problem with empty commits (used in tests).

[adamdubiel]

Done, you can see readme on development branch to see how it will be configurable.

[szpak]

Looks good for me, thanks.