Releases
How we push new code to staging, production, and beyond.
Last updated
How we push new code to staging, production, and beyond.
Last updated
In an effort to keep everything as automated as possible, we have two main protected branches that get automatically deployed in most of our projects:
Pull requests also get deploy previews when applicable.
When a task is finished, it gets merged to develop. When develop is tested and ready to become a production release, the following process takes place:
We run standard-version on develop and take advantage of our Git style conventions to automatically create or update a changelog and bump the version number following semver guidelines.
We push and submit a pull request to master.
We conduct one final review before merging and letting CI/CD take care of the rest.
develop
master
Deploys to a staging environment.
Deploys to a production environment.