Siddhant Medar
c302c1023a
Bugfix/qc qa filetype * WIP: support multi-filetype * Add graceful error handling to QC/QA standalone CLI Wrap validation pipeline in try/except to ensure no partial results are created/uploaded if the pipeline fails mid-execution. * Add comprehensive QC/QA unit tests, improve coverage to 95% - Add CLI integration tests for __main__.py (6 tests) - Add pipeline validation tests for all validation steps (20+ tests) - Test multi-filetype I/O (CSV, XLSX input/output) - Test graceful error handling - Coverage: 43% → 95% * Merge remote-tracking branch 'origin/main' into bugfix/qc_qa_filetype 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.