Alex Galarce
ffb4e07c89
Add time-based rate handling rules and update section labels in prompt templates * Add time-based rate handling rules and update section labels in prompt templates * Add mapping for MyCare Ohio in crosswalk_program.json and update state mapping for Ohio in crosswalk_program_lob.json * Update test parameters and state configuration in testing notebook * Update exhibit-wide payment constraint prompt to exclude administrative processing language * Merge remote-tracking branch 'origin/main' into bugfix/reimb-term-issues * Refine exhibit-wide payment constraint prompt to clarify extraction criteria and examples * Enhance exhibit-wide payment constraint prompt with guidance for abbreviated terms and clarify acceptable constraints * Update SERVICE_TERM prompt to specify healthcare services and clarify extraction criteria 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.