Skip to content

Branching Strategy

This document defines the mandatory branching and pull request rules for all repositories.

🌳 Branch Rules

  • main (or master) represents production-ready code
  • Direct commits to main are forbidden
  • All changes MUST be introduced via Pull Requests
  • Feature and fix branches MUST be short-lived

🔍 Pull Request Approval Policy

  • Every Pull Request targeting main MUST be approved by:
  • The Technical Lead, or
  • The Scrum Master, or

  • A delegate explicitly assigned by one of them

  • The approver is responsible for ensuring that:

  • The implemented changes are aligned with approved User Stories
  • Code quality standards are met
  • Required security tests have passed
  • QA validation has been completed when applicable

✅ Mandatory Pull Request Checks

A Pull Request MAY be approved only if all the following conditions are met:

  • ✔️ Linked to at least one User Story or Work Item
  • ✔️ CI pipeline executed successfully
  • ✔️ Security scans completed with no critical issues
  • ✔️ Automated tests passed
  • ✔️ QA sign-off provided (when applicable)

🛡️ Governance Enforcement

  • Branch protection policies MUST enforce:
  • Minimum one required approver
  • Successful pipeline execution
  • No bypass of required checks
  • Exceptions require explicit approval from Architecture

📌 Notes

  • Approval responsibility cannot be automated
  • Approval implies accountability for production readiness