Introducing PushPreview: GitHub preview deployments made simple
Over the last five years, I’ve been helping companies with their documentation sites. It’s been a rewarding journey, but there was this one issue that kept showing up - enabling pull request previews.
Devs, technical writers, and product owners love pull request previews. When someone updates the docs, a live site builds automatically to reflect the changes. It streamlines the review process and significantly reduces errors.
But here’s the twist: Every company I worked with, big or small, had a tough time setting previews up. The reasons?
1. The cost of setting up and maintaining a parallel infrastructure just for this feature.
2. Some existing solutions require having full admin access to the GitHub org, which is a big NO for most companies.
3. And the support for open-source projects? Most solutions charge per user that triggers previews or by build minutes, which can be exploited. Others, don’t allow external contributors to generate previews at all.
So, I thought “There has to be a better way.” That’s where the idea for PushPreview was born.
Picture this: A simple GitHub Action. You drop a comment saying "/preview" in the pull request, and voila, you get a preview URL. No added complexities. Plus, we’ve added extras like public and private previews, auto-cleaning previews, and role-based auth to fit all sorts of projects.
And hey, I’ve got some exciting news. We’re launching the private beta soon. If you are interested, secure a space at pushpreview.com or drop me a line at hi@davidgarcia.dev.
Can’t wait to hear what you think!
Cheers,
David Garcia
Software Documentation Consultant