Alex Galarce
9cadef9795
Feature/one to one funcs docs and cleanup * Refactor imports and remove unused filter_payer_from_providers function * Update docstring for date_postprocessing function to clarify processing steps * Augment docstrings for check_and_update_effective_date and run_full_context_fields * Enhance docstring for one_to_one_breakout function to clarify processing steps and side effects * remove unused import and augment docstrings 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.