Working Agreement on PR Review and Approvals:
- Senior and Mid need to approve the PR
- PR Shouldn't remain open for more than 2 days
BRANCHING STRATEGY :
We are following Git Flow Branching Strategy in our partner portal , that defines a strict branching strategy designed around the project release. It provides a robust framework for managing larger projects with multiple developers. Here’s a concise explanation of the Git Flow model:
Main Branches
1. main (or master) Branch:
• This branch contains the production-ready code.
• Only stable and tested code is merged into this branch.
• Releases are tagged in this branch.
2. develop Branch(In our scenario its feature_test) :
• This branch contains the latest development changes.
• It is the integration branch for features and fixes.
• It is always kept in a deployable state.
Supporting Branches
1. Feature Branches:
• Branch off from: feature_test
• Merge back into:feature_test
• Naming convention: feature/*
• Used to develop new features for the upcoming release.
• Example: feature/user-authentication
2. Release Branches:
• Branch off from:feature_test
• Merge back into: main andfeature_test
• Naming convention: release/*
• Used to prepare for a new production release.
• Allows for minor bug fixes and preparing meta-data for a release.
• Example: release/1.0.0