Katon Minhas
97281d8ff8
Bugfix/exhibit linking * Crosswalk updates * Merge branch 'main' into bugfix/dynamic-primary-issues * dont include section information in Exhibit Header * Add Molina Health Benefit Exchange to Product-LOB mapping * PPO-POS separate mapping * Prevent inference of LOB from Program or Product * Add SoonerSelect * Update mapping rules to allow for direct values * update prompts * Prep for run * Merged main into bugfix/dynamic-primary-issues * Update unit tests * Update Moda Product mappings * Remove Care1st as Product for Centene * testing * Mapping update * Mapping updates * prep for merge * Merged main into bugfix/dynamic-primary-issues * update prompt template * remove debugs * Remove prints * Merge branch 'bugfix/dynamic-primary-issues' into bugfix/exhibit-linking * Merged main into bugfix/exhibit-linking * Merge branch 'main' into bugfix/exhibit-linking Approved-by: Alex Galarce
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.