branch strategy
There is master branch and separate branches for each team member.
when someone finishes work, they push to their own branch, then after
reviewing it is merged to master.
HOW WE DID IT?
In my project we had master, develop and branch for person. so, if we have
2 automation testers, we will have:
- Master
- Develop
- Tester1
- Tester2
- Tester3
Each tester checks in to their own branches. Then after reviewing it is
merged to develop branch. We merge master and develop only once a sprint.
In my project, our code is separate repo from the application code repo.
Automation framework have a smaller code base and fewer people involved. So,
we can have less complicated branching policy.
My daily automated smoke from Jenkins runs against the master branch.
Master branch is stable since we only merge to with once a sprint.