Siddhant Medar
f7a9d80162
Feature/dtc clean * dtc v1 initial commit * second layer of prompt * Added MAX_PAGES_TO_CHECK and page looping to get answer from llm * Edited contract_type prompt to get cleaner output with no additional text * Updated document_type_classification prompt * Added non-contract type classifcation * Added dtc_v1_test.py for testing only * Updated prompt * Updated prompt * at scale changes * add save feature for individual file output * update dockerfile * clean dtc to prepare for merge * clean up dtc script * Merge remote-tracking branch 'origin/main' into feature/dtc-clean * reafactor code * Merge remote-tracking branch 'origin/main' into feature/dtc-clean 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.