Alex Galarce
cb6284c98f
Small fix to comparisons (lowercase comparison string fields) * Add accuracy calculation to fuzzy matching evaluation * reimbursement primary accuracy test * add match_threshold control * clarify metrics * Merged main into reimb-primary-accuracy-analysis * Merge branch 'reimb-primary-accuracy-analysis' of https://bitbucket.org/aarete/doczy.ai into reimb-primary-accuracy-analysis * add 'billed charges' to reimbursement keywords and update TODO for page checking * add comparisons dictionary * normalize field comparison by converting strings to lowercase * deduplicate data sources in notebook * Merge remote-tracking branch 'origin/main' into feature/add-billed-charges-to-reimb-keywords 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.