Turn off previews for specific PRs
Some PRs don't need a preview. It'd be nice if I could indicate this by putting something like
[preview skip]in the PR title or description.
Echoing what others are saying - it is important that we are able to selectively indicate which PRs should be previews to reduce wasted build and service minutes. My personal preference is that I'd like to see it done in a way where I can add a label to my PR to trigger the preview environment to build, so it's opt-in and not opt-out. But even if it were opt-out like the suggestion to include some special trigger language in the PR description, that would be good too.
Any updates on this?
Now that we're going to be charged for build minutes, I'd _really_ like to be able to disable preview environments for our PRs that only update our readme or other docs. This has been marked as planned for 2 years now, and I hope it can be finished soon.
Bart Van Remortele
I was looking into render as it looks like an interesting solution for our preview environment needs. This one is preventing us from using it however. It would make more sense if we could control this ourselves through a github action. Only deploy on label, destroy when label is removed.
Technically speaking, it is possible to achieve this via API as of today. I'm trying to build a small service on top of Render Cloud for smarter previews.
Skip previews for draft PRs, dependency upgrades, adding tests, documentation changes, specific branches, ...
While this is still unsupported, join the waitlist to be notified when it launches: https://smartpreviews.cloud
Great idea! Strong +1 from me. There are many scenarios - documentation, upgrading dependencies, adding tests, etc - where it would be wasteful to spin up preview. Ensuring my team can continue to make all kinds of incremental updates quickly and in a cost-effective way is essential. Thanks for considering!
Anurag Goel & team, Any update on this? it would be great to have this, as other people mentioned,
dependabotcould create dozens of pr reviews, and in small teams this would have useless review apps running for days.
alternatively, having a github integration to on-demand request review app would be a good option.
Loyu.t: +1 for having the ability to request a preview environment on-demand for a specific branch/PR, as opposed to generating a new environment for every PR by default
Hi Render team,
Any updates on this one?
Preview environments for applications are good as long as you can ignore specific branches/labels and/or text in the PR title.
With dependabot active in bigger node repos, you will often have multiple open PRs that spin up a new environment.
This is a big +1 from my side
Hi Anurag Goel,
Is there an update on this at the moment?
or perhaps an alternative way to ignore certain PRs from being deployed?