Mayank Aamseek
96bb039502
Bugfix/methodology breakout issues * prompt updated * Merge remote-tracking branch 'origin/main' into bugfix/claim_type_1_to_1 * print statements added for testing * test notebook added * Merge remote-tracking branch 'origin/main' into bugfix/methodology-breakout-issues * multiple fee schedule in one term fixed * print statements removed * print statements removed * print statements removed * Merge remote-tracking branch 'origin/main' into bugfix/methodology-breakout-issues * prompt updated to fix mcs issue (row 246) * to fix mcs issue (row 278) * Merge remote-tracking branch 'origin/main' into bugfix/methodology-breakout-issues * special cases and carveouts separated * reverted back unlisted_code carveout_ind value * pipeline error fixed * Merge remote-tracking branch 'origin/main' into bugfix/methodology-breakout-issues * fixes relted to multiple procedure reductions and lesser of * Merge remote-tracking branch 'origin/main' into bugfix/methodology-breakout-issues * breaking special and carveout * code cleanup * Merge branch 'main' into bugfix/methodology-breakout-issues * Merged main into bugfix/methodology-breakout-issues * comments added * lesser of prompt updated to handle nested cases Approved-by: Alex Galarce
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.