VenkataKrishna Reddy Avula
576ea95b6d
DAIP2-112 - fixed get code descriptions * indirect proc codes added * bug fix * bug fix * Merge branch 'main' into proc-code-indirect * description mapping handling X's and 0's * bug fix * Merge remote-tracking branch 'origin/proc-code-indirect' into code-breakout-mismaps * testing mismaps * revenue codes mapping for int values * added function to find ranges * removed test files * Merged main into code-breakout-mismaps * Merge branch 'main' into code-breakout-mismaps pulled latest changes from main * added unit test for find containing ranges * modified find_containing_ranges_test file * Merged main into code-breakout-mismaps * added embeddings to git ignore * updated find_containing_ranges_test.py Approved-by: Alex Galarce 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.