Thanks Rick!

By no means am I saying that this is the best branching strategy out there.

This is just one of the strategies the team concluded on.

I agree on your point on having too many commits. We definitely want to work on that but this model has served us well for now considering our architecture.

Even in a trusted environments, we are all humans, and we want to avoid unsystematic errors. My previous organization indeed had only 1 branch, and it deploys to multiple environments, but it was only dealing with mainly data pipelines. It has its advantages and flaws at the time.

In this organization, we have different branches because the branches are responsible to deploy different versions of data warehouses onto the cloud using Liquibase. We are in the midst of a data migration and there might be flaws in production data, data pipelines etc which we will need to fix. Hence, different versions of data warehouses are required here.

Again, this is comepletely situational as I've mentioned in the article. If you have any suggestions for improvement, I'm all ears!