Mayank Aamseek
722d8aa14a
Feature/daip2 101 * missing group tin fixed * use tin prompt in full context when N/A * fixed N/A TIN and applied same to NPI * null tin fixed * Merged main into feature/daip2-101 * if PROV_GROUP_TIN is still N/A, pick first value from tin_other * Merge branch 'feature/daip2-101' of https://bitbucket.org/aarete/doczy.ai into feature/daip2-101 pulled latest changes from main 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.