Katon Minhas
bb279b45fd
Cnc fl main * prov type moved * comment out invalid prov2 bc it's overly restrictive * Update prompt template to ensure N/A rather than blanks * Update AC multi-prompt template. Update prompts to ensure all keys are present and N/As are filled * Update AC postprocessing * Update clean_tin() to add N/A for values other than 10 digits * update tin postprocessing * Update npi postprocessing * Add 'Filename:' to the start of all filenames * Update group TIN/NPI postprocessing * Update parent agreement code * fix health plan state mapping * Update B postprocessing * Updated indicators, re-ordering * Update postprocessing - all columns included and reordered * Ensure Pages is included in AC-only output * Remove excess print statements * remove example_test to pass pipeline * Fix parent agreement code for AC * Updated postprocessing for NPI/TIN other * Update prompts for N explicitely on AC prompt-based indicators * Updated main and utils for more intuitive filtering * Updated file_counting to match new main process * update test * Add example_test Approved-by: Michael McGuinness
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.