This repository has been archived by the owner on Jun 19, 2023. It is now read-only.
git flow hotfix finish -b still back-merges to develop #390
Comments
adamrodger
changed the title
adamrodger
added a commit
to adamrodger/gitflow-avh
that referenced
this issue
Nov 6, 2018
…etervanderdoes#390 The previous solution still caused a merge to develop, it just performed the merge slightly differently which was misleading. The new solution does not merge to develop at all as the flag description implies.
ChrisJStone
referenced
this issue
in CJ-Systems/gitflow-cjs
Jul 5, 2023
… #390 The previous solution still caused a merge to develop, it just performed the merge slightly differently which was misleading. The new solution does not merge to develop at all as the flag description implies.
ChrisJStone
referenced
this issue
in CJ-Systems/gitflow-cjs
Jul 5, 2023
… #390 The previous solution still caused a merge to develop, it just performed the merge slightly differently which was misleading. The new solution does not merge to develop at all as the flag description implies.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
gitflow-avh/git-flow-hotfix
Line 563 in 9d3592e
When
git flow hotfix finishis passed the-bflag then it's not supposed to mergemastertodevelop, but it does.Steps:
git flow init -d git flow hotfix start 1.0.1 git commit --allow-empty -m "hotfix commit" git flow hotfix finish -b 1.0.1The only difference between with and without
-bis the way in which the merge is made todevelop. What I want is for no merge todevelopat all.The text was updated successfully, but these errors were encountered: