It probably depeds on the kind of software you create, but in our case: When i add non-trivial code I want others of my team to review it first. When it is on

It probably depeds on the kind of software you create, but in our case: When i add non-trivial code I want others of my team to review it first. When it is on trunk, it gets less easier to refactor as others already might use it. In this sense using a MR is really good way to get some quality checks before it goes to main and needs to be supported (in most cases) indefinitely. Next, we have system tests that i really want to avoid breaking on main and getting EVERYONE stuck. The problem arises if I keep that branch for more than a week. Merge conflicts get harder, the financial investment is not leveraged, etc etc. The problem is with long lived branches. This is something you should avoid, you can take it to the extreme, no branches. But extreme is almost never good. PS CC is really good at rebasing and resolving merge conflicts.