We use Fork a lot internally we really love it! Thank you for this awesome work. 😍
There is this one bug that really drove me crazy with the Git flow integration.
If you activate (git flow init) an existing repo (that has 2 active branches, eg: master and develop) the default branch will be tracked correctly but not the second one. Here is an example, on this repo the default branch is develop and as you can see the master is not tracked, we have to manually check it.
Here is the repo config after a git flow init from Fork:
We use Fork a lot internally we really love it! Thank you for this awesome work. 😍
There is this one bug that really drove me crazy with the Git flow integration.
If you activate (git flow init) an existing repo (that has 2 active branches, eg:
master
anddevelop
) the default branch will be tracked correctly but not the second one. Here is an example, on this repo the default branch isdevelop
and as you can see themaster
is not tracked, we have to manually check it.Here is the repo config after a git flow init from Fork:
In fact, it's missing the following:
My workaround right now is to use the cli to activate git flow (
git flow init -d
) this way all the remote branches are tracked correctly.