Praneel Panchigar
ab31139168
Bugfix/preserve lob relationship llm values * Relationship values changes * Fix: Preserve LLM-determined LOB relationship values - Prevent fill_na_mapping from overwriting LLM-determined 'Inclusive' relationships - Only set 'Exclusive' when relationship field is empty/NA (preserves LLM values) - Default to 'Exclusive' when PROGRAM/PRODUCT is NA/blank (LLM bypassed cases) - Condensed redundant conditional logic for better maintainability * Merged main into bugfix/preserve_lob_relationship_llm_values 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.