Alex Galarce
10e534bc77
Enhance reimbursement filtering, extraction, and second-order redundancy checks * Enhance reimbursement methodology documentation with additional valid and invalid examples * Refine reimbursement methodology extraction guidelines for clarity and detail * Add debug logging for methodology breakout prompt and LLM response * Add clarification for non-reimbursement statements in reimbursement guidelines * for exhibit lesser-of processing, add second-order redundancy checks using LLM * Add filename parameter to exhibit lesser-of application and log LLM response for redundancy check * Merge remote-tracking branch 'origin/main' into feature/check-reimb-filtering 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.