Alex Galarce
04cb261831
Rework reimbursement ID to associate parts of "lesser of" (or other such coupled statement) with one another * refactor reimbursement ID generation with hashed service terms * reduce hash length for unique reimbursement ID generation * update reimbursement ID format to include 'exh_pg' for clarity * clean up testing.ipynb * one more formatting fix to testing.ipynb * Move reimb_id generation to postprocessing * move reimb_id function to postprocessing_funcs.py * refactor generate_reimb_ids to group by FILE_NAME and EXHIBIT_PAGE for ID generation * clean testing.ipynb further 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.