>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1050618. --> Reported by: [wizonesolutions](https://www.drupal.org/user/739994) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Some projects use git tag message to define its release notes, so they duplicate them on release node and git tag message.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>To have an optional way for maintainers to activate a two flags:</p> <ul> <li>One for retrieving the message and show it at release node creation.</li> <li>Another for auto-publishing a release based on the last flag.</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/versioncontrol_git/issues/1666622" title="Status: Active">#1666622: Support tag messages</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-4"><a href="https://www.drupal.org/project/versioncontrol_project/issues/2001850" title="Status: Postponed">#2001850: Show git tag message at release node creation</a></span></li> <li><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-4"><a href="https://www.drupal.org/project/versioncontrol_project/issues/2001852" title="Status: Postponed">#2001852: Auto-publishing a release based on the last flag</a></span></li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>Two new options to be added on per-project basis.</p> <h3 id="summary-api-changes">API changes</h3> <p>TBD</p> <h3 id="summary-original-report">Original report by wizonesolutions</h3> <p>As I was testing, I thought of something I hope is a neat idea.</p> <p>If you pass the -a switch to <code>git tag</code>, 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.</p> <p>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 <code>git tag</code> metadata?</p> <p>So, for example, if I type</p> <p><code>git tag -a 7.x-1.0</code><br> *** editor opens ***<br> <code>Here are my release notes.</code><br> *** save and quit editor ***<br> <code>git push --tags</code></p> <p>then when I go to the <strong>Add release</strong> page and select 7.x-1.0 as the tag, on the subsequent screen I would <strong>Release notes</strong> populated with <code>Here are my release notes.</code> Of course, I'd be able to change that if I wanted, but it'd be handy</p> <p>Let me know what you think!</p>