Katon Minhas
2b9bf50c2e
Feature/effective dt * move prompt_smart_chunked to prompt_calls.py * refactor pass_smart_chunked_to_full_context * Mypy fix * Update field to EFFECTIVE_DT * move to prompt_calls * Update vision funcs * Restructure prompt-based date derivation * E2E passed * Remove test * Merge branch 'main' into feature/effective-dt * remove deprecated postprocessing_func * Docstrings * refactor - send global lesser of to prompt_calls.py * remove deprecated function * more docstrings * Merged main into feature/effective-dt * Merged main into feature/effective-dt * added base field for aarete derived effective date Approved-by: VenkataKrishna Reddy Avula
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.