What branching strategies would you recommend for managing code in Bitbucket...

[TerryLambert]

What branching strategies would you recommend for managing code in Bitbucket, and how can we enforce them?

 

Our development team is basically just my brother and I, and we need to choose a consistent branching strategy in Bitbucket to manage our codebase efficiently. So, we need advice on choosing the right strategy (e.g., Gitflow, feature branching) and enforcing it through Bitbucket's branch permissions and merge checks. Thanks!

[Romantin]

Gitflow is solid if you're planning for bigger projects with regular releases, but for a smaller setup, feature branching might suit you better. It keeps things flexible and focused.

[TerryLambert]

Gitflow is solid if you're planning for bigger projects with regular releases, but for a smaller setup, feature branching might suit you better. It keeps things flexible and focused.

 

Thanks for the suggestion! I appreciate it. I’ve heard of feature branching but never came across Gitflow before. Sounds like it could be overkill for our small setup, though. We’ll probably go with feature branching to keep things simple and agile.

 

Any tips on setting up branch permissions and merge checks in Bitbucket to enforce this? Thanks again!