Alex Galarce
b2a0dc4b60
Bugfix/uom * Add "Per Procedure" to valid unit of measure list * Enhance unit of measure prompt for clarity and specificity in reimbursement methodologies * Refine unit of measure prompt to ensure defaulting to 'Per Unit' regardless of procedure codes for flat rate methodologies * Merge remote-tracking branch 'origin/main' into bugfix/uom * Merged main into bugfix/uom * Enhance logic for setting UNIT_OF_MEASURE to 'Per Unit' for Flat Rate reimbursement, handling all edge cases including NaN and empty strings. * Enhance is_empty function to handle additional empty value cases for pd.Series and strings * Enhance test cases for is_empty function to cover additional whitespace and null-like values * Merge branch 'bugfix/uom' of https://bitbucket.org/aarete/doczy.ai into bugfix/uom * Enhance type checking for is_empty function with overloads for str, list, and pd.Series * Overload fix * Merged main into bugfix/uom 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.