Katon Minhas
23af15306b
Feature/new model testing * rename and set up * Setup * Get dynamic primary crosswalked answers * Generate stats for one file * Update dynamic primary evaluation * Multithreading * Set up reimbursement primary evaluation * UPdate output report generation * Update TN calculation * update poetry lock * reorder reimb primary * evaluate 3 models * Configure 4.5 * switch to debug logging * update type checking * Fix mypy * Resolve mypy * Merged main into feature/new-model-testing Approved-by: Karan Desai
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.