Sha Brown
3bf8860ca6
Bugfix/prov info * Added logic to extract provider name from first page * Added prompt to extract provider name from first page * Added prompts and provider name extraction using Hybrid Smart Chunking * Cleaned up code * Added additional logic to check if the provider name on tin/npi page matches provider name extracted from page 1. * Added fix for IS_GROUP issue in provider info json * Remove commented out code * unit test fix * uni test fix * Merge branch 'main' into bugfix/prov_info * Change to string_utils.is_empty * Minor refactor 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.