Alex Galarce
d4ba73dca5
Feature/claude4 duplicate and missing rows * Enhance crosswalk functionality with flatten_to_strings helper and improve value handling in apply_crosswalk * Improve apply_crosswalk function to return original value as fallback when no mapping is found * Enhance apply_crosswalk function to handle empty values and improve defensive programming tests * Enhance reimbursement method prompt to include charge master limitations and improve mapping rules * Merge remote-tracking branch 'origin/main' into feature/claude4-duplicate-and-missing-rows * Refine CHECK_REDUNDANT_LESSER prompt for clarity and detail in evaluating redundancy of exhibit constraints * Enable logging of LLM response for redundancy check in is_exhibit_lesser_of_redundant function * Merge remote-tracking branch 'origin/main' into feature/claude4-duplicate-and-missing-rows * rework prompt for exhibit-wide lesser of * Refine reimbursement methodology guidelines by clarifying invalid entries and examples for risk-sharing * Enhance exhibit linking logic to treat pages with substantial tables as separate exhibits and update function signature to include text_dict. 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.