[cwills]

We have a smallish team working on web apps and use a trunk-based-development branching strategy. Not really to do with helping CI/CD.

The advantage we see is that new developers can start developing as soon as they clone the repository, without needing to switch to the 'development' branch. This is particularly useful when on boarding new developers who are inexperienced with Git. I found that when using Git Flow that the (stable) master branch frequently ends up out-of-date when developers are required to remember to merge into it releases into it.

Diagram of our branching strategy: https://gist.github.com/CameronWills/abf9e307669b1005c88ef82...

[paul_h]

I looked at your diagram. I don;t think you're doing trunk based development.