60c31041198496e484f4d2bccbd419ab27fbfaf3
field/tin npi breakout * additional comments added * pipeline error fixed * final bug fixes during testing * Merge branch 'main' into field/tin-npi-breakout * formatting change - no error otherwise * Merge branch 'field/tin-npi-breakout' of https://bitbucket.org/aarete/doczy.ai into field/tin-npi-breakout pulled latest changes * Streamline tin_npi_funcs * Prompt changes * remove punctuation * Remove duplicates after cleaning * Prompt mods * Update values * Prompt mods - allow for N/A * Prompt for ALL NPIs * Change clean function * Allow multiple group TIN/NPI * Prompt update * Merged main into field/tin-npi-breakout * remove test file * Fix return type * Restore testbed * Merged main into field/tin-npi-breakout * tin_npi_funcs.py edited online with Bitbucket * Removed commented function * Remove regex fields from one-to-one Approved-by: Alex Galarce
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.
Description
Languages
Python
80.5%
Jupyter Notebook
13%
HCL
3.1%
HTML
1.6%
PLpgSQL
1.5%
Other
0.2%