Automated tagging after merge request
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=15962) </details> <!--IssueSummary end--> ### Description Relating to the recommended git workflow, it is quite a lot of manual task involved when releasing a project. ### Proposal There are several slash commands available during `issue` or `merge request` creation helping for fast filling of important information, like `milestone`, `labels` and more. `Merge request` might have a dedicated command, `tags`, that will tag the merge commit of the targeted branch, most common the `master`. ### Links / references ![Feature_proposal](/uploads/cb61fcbf6220b0c4c26823762766d3af/Feature_proposal.png)
issue