-
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
Missing bugfix branches #24
Comments
Well, that's rather arbitrary. I don't think you should hang on to the term "feature" too tight. A rule of thumb would be that if you need more than one commit for a change, you should do it on a feature branch, otherwise commit it directly on develop. Adding another flavour of branches would only make sense if it would be an actual other flavour. What you are referring to are simply feature branches (in that they branch off from develop and merge back into develop). I would advise to name them "fix-" manually, for example: |
Thanks for clarifications. |
👍 |
I came here with the same question. I understand the reasoning but the naming convention doesn't lend itself too well. I think adding "fix" might be something to consider? Just my 2 cents. |
@thiswildorchid I guess it is just convention. Bug fixes and features follow exactly the same process in git-flow. So for all intents and purposes |
I tend to disagree |
My two cents. The name is confusing, but the purpose make sense. There is no value or difference in having another prefix. The rules for such branches will be the same as feature branches. Feature, or topic, branches are about planned changes. The nature of the change is not important. |
I wonnder why bugfix branches are missing in git flow. I think they are the same as features but with different prefix. Are they supposed to live in develop branch as commits without special branches?
The text was updated successfully, but these errors were encountered: