Mayank Aamseek
87f3d2f4f0
Bugfix/mb prompts * reimb primary prompt update * Merge branch 'main' into bugfix/highmark-reimb-primary * prompt reorganised * Merged main into bugfix/mb-prompts * mb prompt refinement * Merge branch 'bugfix/mb-prompts' of https://bitbucket.org/aarete/doczy.ai into bugfix/mb-prompts * Merged main into bugfix/mb-prompts * fee schedule prompt simplified * Merged in bugfix/methodology_breakout_reimb_pct_rate (pull request #831) bugfix/methodology_breakout_reimb_pct_rate to bugfix/mb-prompts * remove case rate from fill empty reimb pct rate * Merged bugfix/mb-prompts into bugfix/methodology_breakout_reimb_pct_rate Approved-by: Katon Minhas * Merged main into bugfix/mb-prompts * grouper breakout prompt changes * Merged main into bugfix/mb-prompts * Merged main into bugfix/mb-prompts * Update reimb primary prompt 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.