You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.
git flow release finish -m "tag commit" 1.0.0 seems to checkout the master branch, merge the release branch, tag, checkout the develop branch, merge the master branch.
git flow hotfix finish -m "tag commit" 1.0.0 seems to tag first, which will place the tag on whatever branch you currently have checked out, then do all the merging. For example, if I currently have the develop branch checked out with new features (for whatever reason), it will place the tag on the latest commit which would be a feature that is NOT currently in the master branch.
can we get git flow hotfix finish to mirror the git flow release finish logic?
The text was updated successfully, but these errors were encountered:
git flow release finish -m "tag commit" 1.0.0
seems to checkout the master branch, merge the release branch, tag, checkout the develop branch, merge the master branch.git flow hotfix finish -m "tag commit" 1.0.0
seems to tag first, which will place the tag on whatever branch you currently have checked out, then do all the merging. For example, if I currently have the develop branch checked out with new features (for whatever reason), it will place the tag on the latest commit which would be a feature that is NOT currently in the master branch.can we get git flow hotfix finish to mirror the git flow release finish logic?
The text was updated successfully, but these errors were encountered: