Feature Request: mversion -a

[blakeembrey]

I just wanted to try out annotated tags so I can start taking advantage of GitHub releases, but having a single line message is a bit difficult to write. Any chance of adding a -a flag that'll set it to annotate and then prompt for the tag message?

Edit: Decided to try it out, but it doesn't seem to tie in with GitHub releases which is a bummer since I kind of like it. I might continue using GitHub releases, but have you found whether it can integrate with tags? It's definitely cleaner and simpler than using a change log.

[mikaelbr]

Hi! See https://github.com/mikaelbr/mversion/blob/master/lib/git.js#L56, annotated tags are automatically used and named the next version number. I use all my libs with annotated tags and github releases as changelog. It should work. What happens on your end and how does it differ feom what you expect?

See for instance https://github.com/omniscientjs/omniscient/releases

[blakeembrey]

@mikaelbr It's the ability to use my default editor for my commit messages, instead of having to put it all in -m. However, it might not be valuable considering when I did that, it didn't populate the "releases" view - I had to manually add the release notes for it to look like the page you provided. I'm guessing you do the same? Tag it, but then use GitHub to do release notes?