COI Policy for requesting PR and branching
Please follow this guideline to create a PR
- We have weekly release with branch name
release/vMajor.MinorVersion every release i.e release/v5.0.0
- If you want to create a PR kindly checkout and create new branch from release branch, please put you type of changes (fix/feature) as prefix. i.e :
fix/scraping-step-bug or feature/login-builder
- commit and push your changes, and ask coi team to review your changes, example : https://github.com/traveloka/coi-common/pull/38
- Title : please put your jira code in title
- Description :
- Summary : describe your summary of changes
- Test plan : tell how do you test your changes
- if your changes get reviewed and already TESTED please squash and merge it to release branch
- Release your changes to stg, test and prod once ready, after that merge your changes to master and create new branch release for next week
- if you want to do 2 or more releases in a week you have to create another release branch with different minor version i.e
release/v5.0.1
- For hotfix you have to checkout your changes from master and create new branch with pattern
hotfix/message/vMajorVersion