Wrong mapping while branch "develop" has been exist.
See original GitHub issueIn my case, i created a branch named “develop” then init the git-flow.
But the prefix configuration came like this on .git/confing
file.
[gitflow "branch"]
master = master
develop = develop
[gitflow "prefix"]
feature = develop
release = feature/
hotfix = release/
support = hotfix/
versiontag = support/
btw, when i init git-flow by bash terminal, everything work fine.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:4
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to change the remote a branch is tracking? - Stack Overflow
If the remote tracking branch does not yet exists but an existing remote tracking branch is currently tracked, it can not be changed...
Read more >How can I tell a local branch to track a remote branch?
When you're starting to work on an existing remote branch. Let's say one of your colleagues has already started and published a branch...
Read more >How to change branch without losing your work - YouTube
In this video Trisha Gee and Gary Hockin demonstrate two ways of keeping work in progress whilst switching to a new branch or...
Read more >Gitflow release branch process from start to finish example
It is only created when the develop branch is feature complete, and it is merged with the master branch once final testing is...
Read more >Why are my commits linked to the wrong user? - GitHub Docs
A user can only access a repository you own if you add them as a collaborator or add them to a team that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks - I’ll look into this!
Fixed in 0.6.1