Show HN: Automatically create QA environments for your GitHub pull requests

Dev here. Our team has grown to love the GitHub pull request workflow. We built Prune to solve one issue we consistently run into: how to QA on the various branches before merging. Happy to answer questions and thanks for any feedback!

&quot;Who are you people?&quot;<p>Why are you committing before making a feature branch, is this part of some flow? (just surprised me a bit) This is as sick as automated CI gets though.

That&#x27;s pretty nice, although... since there are already environments to run tests (e.g. travis) why run them again in Prune, and why not wait until the QA environment is setup to display the notification?<p>I dig the visual regression thing, though I fear combinatorial explosion for big-ish changes if it goes through the whole site or application.

I just set something like this up for a project I&#x27;m working on, using jenkins and (of course) docker. The level of project integration required makes me wonder how easy it is to offer it as a service, but I guess if you can solve that problem you&#x27;ll get customers.

Neat idea.<p>What&#x27;s the underlying technology creating the QA environment? A virtual machine? A container? How is it being configured? A CM tool?

This looks awesome. I love the auto screenshot feature.

How do you manage to support whatever crazy environments a dev may cook up and all the services needed to get a working QA environment set up?

This looks great - Interested to see the pricing - I&#x27;d want to use it across all of our clients projects.

I want this.