Katon Minhas
a910f27cd2
Bugfix/mi dynamic * Refactor - split out one_to_n_cleaning * Rework postprocess * Update postprocessing - fill dynamic values if there is only 1 non-empty value * Update to use string_utils * Group by AARETE_DERIVED_LOB as well * Update crosswalk mapping to handle | lists * Update constants - run with MI flag Approved-by: Siddhant Medar
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.