About experimental git branch workflow
We need a experimental branch besides master which is used for experimenting with new ideas or big changes which may not be successful in the end and not appropriate to mix with other development having less impact. This new branch suggests the review is also separated from the one for the master branch.
So here is the process when we want to try a new unstable feature:
git clone https:/
git review -s
git checkout -b experimental origin/experimental
git checkout -b bug/xxxxxxx
<commits>
git review experimental
When the review workflow is done, our changes will be merged into experimental branch. And when it is stable at some time, we can let the experimental branch rebase onto master and then merge the two with no-ff.
git checkout experimental
git rebase master
git checkout master
git merge --no-ff experimental
Blueprint information
- Status:
- Not started
- Approver:
- Hydrogen Driver Team
- Priority:
- Undefined
- Drafter:
- Le Tian Ren
- Direction:
- Needs approval
- Assignee:
- Le Tian Ren
- Definition:
- Pending Approval
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Aug 14, the new branch was created. https:/
Aug 14, PoC was done. https:/
Work Items
Work items:
Create experimental branch : DONE
POC https:/