Katon Minhas
ac6dfdb721
Bugfix/mcs issue fixes * Update code primary prompt * Merge branch 'main' into bugfix/mcs-issue-fixes * No longer treat non-reimbursement tables as 'tables' for the purpose of preprocessing * No longer extract Reimb Effective Date from footer of the page * Merge branch 'main' into bugfix/mcs-issue-fixes * Update unit tests * Add postprocessing step to remove Reimb Date values when the 1:1 date values are identical * Update unit tests * prep for merge * Remove excess prints * Merged main into bugfix/mcs-issue-fixes * Merge branch 'main' into bugfix/mcs-issue-fixes * Prep for merge * remove print 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.