We have set the policies for branches to make rules and technical checks, but the question is, how swap use branches in Git to support your work? Which strategy should you use? When should you create a new branch? When should you merge branches?
There are plenty of strategies you can use, and there is no silver-bullet solution. The best strategy for your team could be different for another team, or you may have one strategy for your AppSource app and another for your PerTenant app.
Before you decide which way you will go, think about the KISS principle (Keep It Simple, Stupid).
In all of the examples in this chapter, we will consider the master branch the most stable one, the one that represents the app as it is released to production. You can decide to name this branch differently and it has no impact on the strategies themselves. You just need...