e161142ea59ab93da65b907136afc50c92c5ba21
Sonnet 4 and model aliasing * Add EXHIBIT_HEADER_MARKERS for improved document header recognition in table handling * Refactor EXHIBIT_HEADER_MARKERS definition for improved clarity and organization * remove unused page span tracking code; add unit tests for new functionality * remove debugging logs from combine_continuous_tables function * Refactor logging setup and update test file configuration in investment field testing notebook * Merge remote-tracking branch 'origin/main' into feature/further-phase-1-and-2-fixes * Merge remote-tracking branch 'origin/main' into feature/further-phase-1-and-2-fixes * Refactor model ID handling and add support for model aliases in llm_utils * Update model IDs to use alias in LLM invocation functions in one_to_n_funcs * change pre-and-post-processing to new model alias method * Update model ID references to use 'sonnet_latest' in LLM invocation functions * Update LLM invocation functions to use 'sonnet_latest' model ID * Update LLM invocation functions to use 'sonnet_latest' and 'haiku_latest' model IDs * update invoke_claude function docstring * Fix caller frame to address mypy error 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.
Description
Languages
Python
80.5%
Jupyter Notebook
13%
HCL
3.1%
HTML
1.6%
PLpgSQL
1.5%
Other
0.2%