Skip to content

Conversation

ChrisJStone
Copy link
Member

This is a re submission of PR 395 in reference to issue 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.

…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 ChrisJStone self-assigned this Jul 5, 2023
@ChrisJStone ChrisJStone added this to the 2.2.0 milestone Jul 5, 2023
@ChrisJStone ChrisJStone linked an issue Jul 5, 2023 that may be closed by this pull request
ChrisJStone added a commit that referenced this pull request Jul 5, 2023
)

fix(hotfix): fix nobackmerge flag

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.

closes #21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

fix: git flow hotfix finish -b still back-merges to develop
2 participants