v2.0.0
This release introduces a great new feature and way for developers to safely release their changes without stepping on each other's toes
Introducing Branch Deployment Locks 🎉
About Deployment Locks
Just like how you can comment .deploy on a pull request to trigger a deployment, you can also comment .lock to lock deployments. This will prevent other users from triggering a deployment. The lock is associated with your GitHub handle, so you will be able to deploy any pull request in the repository and as many times as you want. Any other user who attempts a deployment while your lock is active will get a comment on their PR telling them that a lock is in effect
To release the deployment lock, simply comment .unlock on any pull request in the repository at anytime. Please be aware that other users can run this same command to remove the lock (in case you get offline and forget to do so 😉)
Running .lock --info at any time will retrieve lock details about the current lock (if it exists)
You can read more about deployment locks in this repo here
Happy deployments! 🚀
What's Changed
Below is the detailed list of all the changes that went into this version
Beyond deployment locks, this release also adds a lot of minor fixes, improvements, and additional documentation
- Deploy Locks 🔒 by @GrantBirki in #30
- Deploy lock improvements by @GrantBirki in #31
- Lock output improvements by @GrantBirki in #32
- Sticky Lock Output Improvements by @GrantBirki in #33
- Remove lock after deployment and fixes by @GrantBirki in #34
- Lock docs by @GrantBirki in #35
- Lock flags and alias by @GrantBirki in #36
- Usage Guide by @GrantBirki in #38
Full Changelog: v1.5.0...v2.0.0
