Alex Galarce
7038a92d10
Bugfix/medicare advantage duals * Add logging for debugging in crosswalk utilities and mapping functions * Add debug logging for crosswalk processing and mapping in get_crosswalk_fields * Add logging for dual LOB check prompts and responses in update_lob_for_duals * Enhance dual LOB check logic to ensure PROGRAM and PRODUCT fields are empty before proceeding * Update dual LOB check to use AARETE_DERIVED fields for validation * Refactor logging in fill_na_mapping and get_crosswalk_fields for clarity and conciseness * Remove debug logging from get_lob_relationship for cleaner output * Remove debug logging from apply_crosswalk for cleaner execution 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.