Some projects use git tag message to define its release notes, so they duplicate them on release node and git tag message.
To have an optional way for maintainers to activate a two flags:
- One for retrieving the message and show it at release node creation.
- Another for auto-publishing a release based on the last flag.
User interface changes
Two new options to be added on per-project basis.
Original report by wizonesolutions
As I was testing, I thought of something I hope is a neat idea.
If you pass the -a switch to
git tag, you can enter a message that's as long as you like. Git resources often suggest using this to contain your release notes or something about what the tag means.
This could be useful metadata to d.o. How about pre-populating the release notes on step 2 of the "Add release" page with the
git tag metadata?
So, for example, if I type
git tag -a 7.x-1.0
*** editor opens ***
Here are my release notes.
*** save and quit editor ***
git push --tags
then when I go to the Add release page and select 7.x-1.0 as the tag, on the subsequent screen I would Release notes populated with
Here are my release notes. Of course, I'd be able to change that if I wanted, but it'd be handy
Let me know what you think!