Read on Twitter
It's probably common knowledge that Netlify makes deployment incredibly simple- you can connect a repo, pick a build command and 
or just drop a folder in and you're done!
...but here are some other things you might not know about our deploys that are very special
Netlify has a concept of "atomic" deploys- which means a few things:
- You can preview a deploy when you've or someone else has just put in a PR
- You can roll back to ANY previous state, with one click, in milliseconds
- You always know what state your cache is in!
- You can preview a deploy when you've or someone else has just put in a PR
- You can roll back to ANY previous state, with one click, in milliseconds
- You always know what state your cache is in!
Netlify allows you to cancel a deploy- did you just put in a change, merge it and then realize you've made a terrible mistake? I've never done that. 
er...
No worries. You can cancel that deploy with the click of a button.
er...No worries. You can cancel that deploy with the click of a button.
You can lock a deploy. Let's say you get everything ready for a big release, code review and tests are complete, it's all ready.
You can lock a deploy in a state to get ready for a major release, so that you know exactly what you're releasing and sleep well the night before.
You can lock a deploy in a state to get ready for a major release, so that you know exactly what you're releasing and sleep well the night before.
You can even get notifications about locked deploys via email, outgoing webhook, or Slack. Netlify can notify you when a deploy is either locked or unlocked.
You can skip deploys! Let's say you have a bunch of dependabot changes and you want to merge them without redeploying the site multiple times.
You can add [skip ci] or [skip netlify] to the most recent commit message, and it will apply to all other commits in the push.
You can add [skip ci] or [skip netlify] to the most recent commit message, and it will apply to all other commits in the push.
You can download a deploy!
Let's say you were curious about what your site looked like 4 years ago. Aside from the fact that you can actually just redeploy that version of the site since it's atomic, you can also download that version in time, and revisit your older approach!
Let's say you were curious about what your site looked like 4 years ago. Aside from the fact that you can actually just redeploy that version of the site since it's atomic, you can also download that version in time, and revisit your older approach!
The last one is my fave- you can use different branch deploys for split testing! You don't have to incur heavy JS costs of A/B testing frameworks. You can send traffic to different versions of your site, and add google analytics to the different branches too :)
That's it! I hope this has been helpful. For more information you can visit our docs:
- https://url.netlify.com/B1HqHw7gO
- https://url.netlify.com/BJNhHDQe_
- https://url.netlify.com/B1HqHw7gO
- https://url.netlify.com/BJNhHDQe_
