Alex Galarce
273d124d09
Feature/na blank handling * Update prompts to clarify responses for unknown vs N/A values * Update code description mapping to differentiate between empty and unknown grouper codes * Update prompts and code descriptions to standardize 'unknown' to 'UNKNOWN' * Update PIPE_FORMAT_INSTRUCTIONS to replace 'concept' with 'requested information' * Merge remote-tracking branch 'origin/main' into feature/na_blank_handling * Merged main into feature/na_blank_handling * Update NPI prompt for clarity and detailed instructions * Enhance TIN prompt for clarity and detailed identification instructions * Merged main into feature/na_blank_handling * Merged main into feature/na_blank_handling 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.