Alex Galarce
b2a8e77cca
refactored code to add recent health plan state hotfixes into the existing postprocessing pipeline * refactored code to add recent health plan state hotfixes into the existing postprocessing pipeline * Merged main into chore/health_plan_state * Merged main into chore/health_plan_state * add debug print statement * debug print statements * more debug print statements * print df columns for debug * move health plan state hotfix functionality to postprocessing_funcs.py * add better error printing * add error message for parent agreement code * remove dots in state abbreviations * remove unused import * also look for state abbreviations * Merged main into chore/health_plan_state * remove print statements * Merged main into chore/health_plan_state 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.