Branching Strategy (2026)

Index: 

• Branching Cycle
• Bugfix in non-dev branch
• Feature/Bugfix to Dev
• Shared feature implementation

About

These pages contain information about the current branching strategy, and how to act as a developer/tester on certain actions in the process.

Why

It is important to follow the guidelines of the branching strategy because:

• Your colleagues rely on the things you do
• The strategy ensures the stability of the codebase
• The strategy supports a stable product

Overall strategy

The overall strategy is, that the code implementation is ALWAYS done in the following order:

DEV-TEST-STAGING-PROD

This way, we ensure that the NEWEST code is ALWAYS in the branches to the left.

There will NEVER be any code in right-side branches that does not exist in the left side branches.