Branching Strategy

All Backend and DevOps repos will abide by the same branching strategy. The strategy chosen will be:

• One branch per environment

• Deployment on push to branch

This branching strategy is simple and secure, in the way that what you see on the branch is what is deployed in the environment.

The git branches should be named after the environments:

• dev

• staging

• production

Dev branch will be the default branch. Environment branches will be protected from force push among other protection measures.

All changes to the code should be deployed to staging and tested/verified in this environment before merging them into production.