Alex Galarce
425a8ec86c
Feature/per file logging * Add custom per-file logging handler * Add close method in PerFileHandler to properly close file handlers * Add return type annotation to setup_per_file_logging function * Set up per-file logging in main and process_file functions * Add per-file logging configuration options and update setup logic * Refactor logging setup in testing notebook to use per-file logging and improve organization * Clean up whitespace and improve organization in testing notebook * Merge remote-tracking branch 'origin/main' into feature/per-file-logging * Enhance per-file logging setup by adding debug level configuration and informative print statement * Change logging from info to debug level in table processing functions for improved verbosity control * isort 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.