Karan Desai
72f633cad2
Bugfix/reimb primary * prompt update for reimb primary * reimb primary prompt update to extract more info * prompt update at to priotrize $ amounts * prompt update for split tbales * updated valid entries for reimbs * addition to reimb primary prompt * reimb primary pormpt update * Merge remote-tracking branch 'origin/main' into bugfix/reimb-primary merhing latest main in reimb-primary * Merged main into bugfix/reimb-primary * fix- PR comment 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.