Alex Galarce
c6313460fc
Small bug - reversed testbed and results in page-level row counts * Add page-level row count comparison to analyze discrepancies between testbed and results * Fix key naming in page mismatch comparison for consistency * Merged main into feature/row-count-by-pages * Implement page-level grouping and comparison for row counts in testbed and results * Fix row count difference calculation in page comparison * Merged main into feature/row-count-by-pages * Fix exhibit page normalization logic in group count calculations 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.