3 years ago

Category: Database, github

In a recent blog post, I discussed expanding the idea of “Feature branches” to “Feature environments”. Using Infrastructure-as-Code, we can create an environment for every feature we are working on, thereby giving us a more flexible, isolated development environment, and allowing us to test our code early in the development process. In this post I’d like to continue down that path, and see how we can automatically create an environment for every pull request, and gain a number of advantages over traditional static staging or QA environments.

PR’s are more than just a code review — they’re a milestone in a feature’s lifecycle and a way of saying “I’m ready for this to be shared”.

We now have a fully functioning pipeline, and our setup will automatically create a new environment for every PR we open!