Alex Galarce
95fe703137
Fields/document dates further iteration * add concise date fix prompt * Refactor and prepare for postprocessing formatting * Merged main into fields/document-dates-further-iteration * Merged main into fields/document-dates-further-iteration * Implement memoization for date postprocessing and add derived termination date calculation * Merge branch 'fields/document-dates-further-iteration' of https://bitbucket.org/aarete/doczy.ai into fields/document-dates-further-iteration * fix mypy error * tweaks to derived termination date * Add docstring to derived_term_date_prompt and create unit tests for prompt generation * fix memoization in postprocess.py * Merged main into fields/document-dates-further-iteration 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.