Open erikhuizinga opened 7 years ago
Aha, I see! I think another use case could be one where you have an additional main branch besides master and develop. But since the git flow support branches aren't meant to be merged ever, this would not work. We'll see when more documentation is available.
On Wed, 17 May 2017, 19:41 John Mercier, notifications@github.com wrote:
I believe this is answered in the faq https://github.com/nvie/gitflow/wiki/FAQ and here http://stackoverflow.com/a/16866118/1997707. The idea is to support previous releases. It may be difficult to hotfix a 1.0 when you already have 2.0 and 3.0 in master. In some cases you may not need that hotfix in 2.0 or 3.0 either.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvie/gitflow/issues/6389#issuecomment-302170146, or mute the thread https://github.com/notifications/unsubscribe-auth/ASeikE6vFxrZgOZLTzvuhUZ4RI7nsgToks5r6zFUgaJpZM4Ndo5s .
I would consider using gitflow-avh. This project seems dead.
Looks great, I'll consider switching to that version.
On Thu, 18 May 2017, 16:56 John Mercier, notifications@github.com wrote:
I would consider using gitflow-avh. This project seems dead.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/nvie/gitflow/issues/6389#issuecomment-302429336, or mute the thread https://github.com/notifications/unsubscribe-auth/ASeikAByZuJFB58gi6CbPQfsxDdxG7RXks5r7FwggaJpZM4Ndo5s .
I see an experimental option to start a support branch using
git flow support
. What the intended use case for support branches? The original article doesn't describe support branches other than feature, release and hotfix branches, which are already implemented in differentgit flow
commands. Isgit flow support
intended for custom workflows in which additional support branches are required?