Skip to content

Latest commit

 

History

History
9 lines (9 loc) · 627 Bytes

release.md

File metadata and controls

9 lines (9 loc) · 627 Bytes

Steps to follow release(Chargebee owned)

  1. Assume release is 0.0.9. (find release from git page release section)
  2. create a new branch called release/ so this would be release/0.0.9
  3. create new branch for ticket feat/
  4. commit to feat/
  5. Raise PR from feat/ to release/0.0.9
  6. After PR is approved and merged
  7. Raise PR from release/0.0.9 to dev. Once PR is merged it will auto release the 0.0.9 version of SPI for dev code base
  8. After that raise PR from release/0.0.9 to main. Once PR is merged it will auto release the 0.0.9 version of SPI for prod codebase