Recently, it has become common practice for development teams to deploy their code multiple times a day, and new developers are encouraged to do so on their first day of work.

In this talk, I'll explain how I use continuous deployment to take these practices to the extreme. Automatically deploying the master branch as new changes are made is a great way to improve your development process.

Automatic master deployment will fundamentally change the way you work. The days of epic pull requests are over. You'll quickly find yourself writing smaller, more manageable blocks of code that, overall, have a big impact on the quality of the software you build.

By the end of the talk, you'll know how to change the GitHub merge pull request button to a deploy button—and have the confidence to do it.

Some things I will go through in the talk:

How to set up your CI environment for deployments
Why rapid tests are important
How to use your staging environment to test deployments
How to use feature flags to hide deployed features from some users
Deployment without downtime, even during database migrations
Your new deployment button, also known as GitHub Merge Pull Request button
What to do if deployment fails

Help us subtitle and translate this video!

http://amara.org/v/FGZB/

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.