Alex Galarce
0230d07dda
Feature/split reimbursements * Update reimbursement test cases to reflect accurate reimbursement terms and improve deduplication logic * move VALIDATE_REIMBURSEMENTS_PROMPT to investment_prompts.py * black, isort formatting * Remove IDENTIFY_REIMBURSEMENT_EXHIBITS_PROMPT function (unused) * Add MODEL_ID_CLAUDE4_SONNET for new model integration (doesn't work right now) * pipe delimited-output and parsing * Merge remote-tracking branch 'origin/main' into feature/split-and-filter-reimbursements * Merge remote-tracking branch 'origin/main' into feature/split-reimbursements * Add functionality to split compound reimbursement terms into distinct methodologies * splitting logic for reimbursement terms * put in split compound reimbursement step * Fix JSON output formatting in reimbursement terms example * reimbursement splitting: move prompt to investment_prompts.py, move keywords to investment_values.py * Merge remote-tracking branch 'origin/main' into feature/split-reimbursements * Merge remote-tracking branch 'origin/main' into feature/split-reimbursements * Change order (split -> filter over filter -> split), improve logging * Refactor reimbursement filtering logic to use a two-stage approach with pattern-based negative filtering and LLM validation * Replace clear reimbursement indicators with obvious non-reimbursement indicators for improved clarity in reimbursement filtering * Simplify reimbursement filtering by removing pattern-based checks and relying solely on LLM validation * Remove obvious non-reimbursement indicators from reimbursement filtering keywords * Enhance reimbursement level test by adding LLM validation and updating mock return values for service terms * Merge remote-tracking branch 'origin/main' into feature/split-reimbursements * Fix failing test * Merge remote-tracking branch 'origin/main' into feature/split-reimbursements * update mock return values to fix failed tests Approved-by: Siddhant Medar
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.