-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable releases from support branches #239
Comments
Hello, I think this could be quite hard to achieve. If you derived a release branch from a support branch, how do you know you must merge back in the support branch instead of following the default workflow? I wonder if such branches do not deserve subcommands, like
With configured prefix for such branches that do not fall under already configured prefix. We may even use subcommands to make hotfix on release branches:
Regards. |
|
+1 for this |
I'll make some implementation test based on Peter van der Does fork. I have the idea of factorizing the code with actual Regards. |
@baby-gnu Please wait with the coding. I have another idea that may actually solve this in another way, See: petervanderdoes/gitflow-avh#43 @hugoduncan Can you tell me how you use the Support branches? You are one of the 1st people I have heard that use support branches extensively. |
@petervanderdoes I have an infrastructure automation project, https://palletops.com, https://github.com/pallet/pallet, that requires maintenance of previous releases. Currently I use develop is for the next major version of pallet, while still supporting the current release version on the support/0.7.x branch. There are still some fixes that get backported to the support/0.6.x branch (though non recently). |
@hugoduncan Thanks, that's what I believed that support branches were supposed to be. I will work on the petervanderdoes#43 and that way you can do hotfixes, features, releases from support branches as well. |
@petervanderdoes that would be fantastic! and certainly seems to be the "right" way of doing it. |
We've used support branches fairly heavily, and miss the ability to have
git flow release
work sanely on these. A release from a support branch should not merge to the release branch.Does it make sense for
git flow release
to work on a feature branch, by creating a release branch and merging the release back into the support branch ongit flow release finish
?The text was updated successfully, but these errors were encountered: