Karan Desai
5887cf651e
Feature/pc * file read update * removed unused code * replace pring with logging.info * input args for docczy output * input args for docczy output * added json for loading mappings * exception for bool keys * exception for bool keys * added init.py * write to s3/local functionality * write to s3/local functionality * logging errors and main functionality fix * pc functionality from main * pc functionality from main * function signature fix * fixed path returns * Updated names for varaibles; Modified termination date cleaning function * Removed commented out function * Renamed client column names to SAAS column names * Merge remote-tracking branch 'origin/main' into feature/pc * removed pc utils * black formatting * rename function * rename func * additional file removed 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.