Alex Galarce
39a07f63c9
pyproject requirements, prep for logging fixes * remove chroma * update project name to "doczy-field-extraction" in pyproject.toml * update lock file * replace print statements with logging for better traceability in process_file function * replace print statements with logging for improved error tracking and information logging * replace print statements with logging for improved error handling and traceability * replace print statements with logging for improved error handling in llm_utils and string_utils * remove unused table_utils module; supplanted by table_funcs and unreferenced * replace capsys with caplog in test_invalid_input_type for improved logging of invalid input 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.