Actually my workflow has kinda change since this post. That I create an epic branch which are versions like v1. Then task branches that are features to be done for v1 release. Also I now name them "jr.create-book" adding my initials to the branch.
Anyways, regarding the epic branches. I think you should only do it for features that are too big then chop then it up into little pieces. Since it is easier to review small PRs than bigger ones that does a lot.
Regarding what you've said above. You can create an epic branch called "feat-book-page". Then three task branches called "task-book-page-create-book", etc. that points to the epic branch. So when you create a PR also a preview deployment, you can test the book page (epic branch) before merging it to production for all to see.
Quite similar to GitFlow, i recently found a vscode extension that handles all the git commands to create feature branches (Task Branches), release branches (Epic Branches), if you are interested here is the link to it.
Hi, really nice works! It helps me a lot, i was always struggling to have a nice streamflow.
I'm not sure i fully understand how you manage epic with your branch
If we have one Epic
Book Page
And 3 tasks
Create Book
Read Book
Delete Book
What branchs do you create ?
1 for the epic and one for each task?
Thanx a lot for your work
Actually my workflow has kinda change since this post. That I create an epic branch which are versions like v1. Then task branches that are features to be done for v1 release. Also I now name them "jr.create-book" adding my initials to the branch.
Anyways, regarding the epic branches. I think you should only do it for features that are too big then chop then it up into little pieces. Since it is easier to review small PRs than bigger ones that does a lot.
Regarding what you've said above. You can create an epic branch called "feat-book-page". Then three task branches called "task-book-page-create-book", etc. that points to the epic branch. So when you create a PR also a preview deployment, you can test the book page (epic branch) before merging it to production for all to see.
Thanx for your answer :) i'll try it and adjust to my needs ;)
Quite similar to GitFlow, i recently found a vscode extension that handles all the git commands to create feature branches (Task Branches), release branches (Epic Branches), if you are interested here is the link to it.
marketplace.visualstudio.com/items...