Alex Galarce
485859e954
Bugfix/chroma too many files * Add emergency cleanup and monitoring for vectorstore cache * Refactor vectorstore handling and enhance file descriptor monitoring in field_context * Refactor vectorstore cleanup logic to ensure safe reference counting and improve error handling * Enhance monitoring and cleanup mechanisms to prevent file descriptor leaks in smart chunking functions * Add garbage collection to safe_process_file for improved memory management * Refactor docstring in safe_process_file to clarify error handling and resource cleanup details * isort * Enable Chroma reset functionality for improved resource management and logging 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.