Alex Galarce
da174ceefa
default term new prompt and de-duplication before Methodology Breakout * Refine prompts for default indicator methodology and enhance instructions for final reimbursement methodology output * Enhance DEFAULT_INDICATOR prompt to clarify its role as a fallback reimbursement method * Implement service-reimb tracking to prevent duplicates * Refactor methodology breakout processing to reduce code duplication and improve clarity * Remove debugging print statements and improve item ID formatting in reimbursement processing * Merge remote-tracking branch 'origin/main' into feature/default-term-new-prompt * Refactor methodology breakout processing to remove duplicate tracking and simplify logic * Merged main into feature/default-term-new-prompt * Merged main into feature/default-term-new-prompt * rename _process_answer_dict to _process_carveout_or_breakout 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.