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.
Because there are no git flow {bugfix,feature,hotfix,support} move <name> or git flow {bugfix,feature,hotfix,support} rename <name> commands, one is forced to instead use the vanilla git branch -m <old-branch> <new-branch> command which won't update the moved/renamed branch's corresponding "[git flow ...]" section within the .git/config file.
This leads to problems like the following:
$ git branch -m feature/old feature/new
$ git flow feature start old
Fatal: Branch 'feature/old' already exists. Pick another name.
The text was updated successfully, but these errors were encountered:
This is related to #407 in that there should be a corresponding git flow command for every vanilla git command that can potentially invalidate the "[git flow ...]" sections within the .git/config file.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Because there are no
git flow {bugfix,feature,hotfix,support} move <name>
orgit flow {bugfix,feature,hotfix,support} rename <name>
commands, one is forced to instead use the vanillagit branch -m <old-branch> <new-branch>
command which won't update the moved/renamed branch's corresponding "[git flow ...]" section within the .git/config file.This leads to problems like the following:
The text was updated successfully, but these errors were encountered: