问题
my current workflow to handle and resolve issues in GitLab is the following (I will define the problem after it):
- create a milestone with connected release tag via Release API
- connect issues to the milestone
- automatically create MRs and branches connected to the issue via GitLab UI (for consistent naming)
- Make MR changes
- Merge MR and close the issue automatically
The problem here is how I handle the tag. Its absolutely not a part of the updates workflow because when I create it, it gets the latest master before I make the changes.
But how do I bind all my changes under a release version?
One idea was to merge all changes into a release branch and to connect this branch to the tag but the problem is GitLab doesn't close the issues either their MRs are merged with the release branch or when the release branch is merged. And this is a problem because the milestone overview would become redundant.
回答1:
Tags aren't really meant to work that way. Generally they are used to mark a point in the repo's history that has certain functionality. Frequently this is a release name/number or version number.
It looks like your same workflow will work if you just move the tag to the end, after you've merged the MR into master.
You can read up on tags in the git documentation here.
来源：https://stackoverflow.com/questions/59248030/git-how-to-bind-changes-of-multiple-mrs-under-a-new-release-tag-version