VenkataKrishna Reddy Avula
4576ffbb91
Feature/outlier fields to Main * modified existing outlier prompts and definition * Merged main into feature/outlier_fields * updated prompts * updated prompts * Merged main into feature/outlier_fields * updated outlier definition * added outlier terms to dynamic funcs * added allow na for outlier terms * added outlier breakout * Merged main into feature/outlier_fields * added 2 stage breakout * error fix * Merged main into feature/outlier_fields * removed comments * fixed reimb outlier cases * Merge remote-tracking branch 'origin/main' into feature/outlier_fields 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.