Katon Minhas
036052e75f
Hotfix/Exhibit * Initial draft - Exhibit test * Update logic * Add Exhibit page_num column, add pipe format to prompt * Working test * Update LOB to check new Exhibit * Greenlight file commit - needs minor efficiency improvement * Reordering, intermediate file saving, Exhibit+LOB Fix * Merged main into Exhibit branch * removed excess print statements * Merged main into hotfix/Exhibit * Updated valid lists for mapping, reconfigured for rerun filter * Extra print * added fixes for batch 7 * added fixes for batch 7 * Merged main into hotfix/Exhibit * apply_cnc_hotfix.py edited online with Bitbucket 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.