Alex Galarce
dcde32e7af
Feature/test bed facilitation for 1-1 fields * start comparing output to label data * Enhance load_test_files.py to merge and reorder labels and predictions, outputting to CSV * Refactor load_test_files.py to streamline label and prediction loading, sorting, and CSV output for date and TIN/NPI fields * rename to one_to_one_comparison * Merged main into feature/test-bed-facilitation * rename notebook_config * Merge branch 'feature/test-bed-facilitation' of https://bitbucket.org/aarete/doczy.ai into feature/test-bed-facilitation * Merged main into feature/test-bed-facilitation 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.