Answer the question
In order to leave comments, you need to log in
How to properly organize feature branches in gitflow?
I understand git-flow, a question immediately arose:
for example, there is a task that consists of separate subtasks of the type
1. add a new feature section to the personal account
2. add a new feature section to the admin panel
3. add functionality from these sections to different parts of the site
4. and etc.
How to organize it correctly?
Google told me that "each task needs its own feature branch branched from develop", but this is inconvenient.
It is more convenient to make a parent Feature and branch off small tasks from it.
Is this the norm? How are you doing?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question