Mayank Aamseek
7e863f5fc8
Bugfix/Molina UT conversion factor * handle multiple default_terms in one reimb_term * remove incorrect trigger cap cases * carveout_cd fixes * Merge branch 'main' into bugfix/Molina-UT-carveout-cd * fix variable naming * methodology prompt updated * Merge branch 'main' into bugfix/Molina-UT-carveout-cd * revert test changes * revert test changes * fixed incorrect conversion factor * Merge branch 'main' into bugfix/Molina-UT-conversion-factor * test to fix service term * Merge branch 'main' into bugfix/Molina-UT-conversion-factor * revert test changes * Merged main into bugfix/Molina-UT-conversion-factor Approved-by: Katon Minhas
Branching and Release Management Guide
Overview
This guide outlines the naming conventions, branching strategy, and merging process for our Git repository.
Branch Naming Conventions
- Feature Branch:
feature/<name>- Example:
feature/add_build_stage
- Example:
- Bugfix Branch:
bugfix/<name>- Example:
bugfix/pages_duplication
- Example:
- Hotfix Branch:
hotfix/<name>- Example:
hotfix/deployment_failure
- Example:
....
Branching Strategy
Creating Branches
- Create a feature branch from
mainusing the appropriate naming convention. - Create a small and complete change.
mainmust always have deployable code. - Create a Pull Request back to
main. - Ensure all checks have passed.
- Merge new code.
- Ensure the functionality is verified in the dev environment.
Refer to the branching guide in Confluence for more info on this
This guide ensures that all team members follow the best practices for branch management and releases.