Sha Brown
77c845a82e
Bugfix/prov info issues * Initial commit * Passed payer name to tin npi llm call to avoid assigning tin npi to payer * Removed record that contains NO_IDENTIFIERS_FOUND from PROV_INFO_JSON * Updated unit test for test_tin_npi_funcs * Changed name check code back to original to be consistent * Updated test_tin_npi_funcs.py to pass in payer_name in functions * Add fix to unit test * Updated output in unit tests * Merged main into bugfix/prov-info-issues 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.