452a2de7d0be35ceee4ac322cb87466e705023e1
Bugfix/NTE num rows to Main * updated REIMB_TERM_BREAKOUTprompt * Merged main into bugfix/NTE_num_rows * updated NTE prompt * updated reimb_pct_rate prompt * updated reimb_method prompt * added cost prompt in reimb method * Merged main into bugfix/NTE_num_rows * conflict fixes * Merged main into bugfix/NTE_num_rows * updated prompts 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%