VenkataKrishna Reddy Avula
8ec2561a68
Bugfix/special cases to Main * prompt update * Merge branch 'main' into bugfix/json_and_unit_of_measure * minor bugfix * minor bugfix * prompt update for outlier rate * added outlier testing jupyter notebook * Remove special case from any empty * updated outlier breakout prompt * Merged main into bugfix/special-cases * reimb_method minor fix * Merged main into bugfix/special-cases * bugfix field to add dynamic funcs * merged with main * latest outlier changes * Merged main into bugfix/special-cases * added table guidelines for special case primary * updated special case primary prompt * Merged main into bugfix/special-cases * updated special case primary table handling * merged main into bugfix special cases * Merged main into bugfix/special-cases * Remove test notebooks from tracking * trying out pipeline fix * reverted chnages * pipeline fix 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.