Review links for preview deploys

Every branch or pull request that Vercel, Netlify, GitHub or GitLab deploys gets its own review link, which follows the latest deploy.

Team members2 min

Preview deploys are on paid plans. Set them up in the project's Settings › Preview deploys; anyone who can edit the project can.

What you get

One review link per branch or pull request. When a preview finishes deploying, Plotter makes a review link that opens it, labelled with the branch or PR number. Copy it from Recent previews.
Redeploys keep the link. A new deploy of the same branch moves the same link to the new preview, so the address you shared keeps working.
On GitHub, the link is posted on the pull request once, as a comment.
Production deploys are skipped. Marks made on a preview land in the project's current round with every other task.

Open the project's Settings › Preview deploys and choose Add Vercel, Add Netlify, Add GitHub or Add GitLab.
Follow the steps shown. For Vercel, Netlify and GitLab, Plotter gives you an address to paste into the provider's webhook settings, and a secret that proves the calls are real (see below).
Push a branch. Its preview appears under Recent previews with a link to copy.

Provider	Where	Secret
Vercel (Pro and Enterprise teams)	Team Settings › Webhooks, event deployment.ready (and deployment.succeeded if offered)	Paste Vercel's secret back into Plotter
Netlify	Site configuration › Notifications › Deploy notifications › HTTP POST request, event Deploy succeeded	Plotter's JWS secret
GitLab	Settings › Webhooks, Deployment events	Plotter's secret token, or a signing token GitLab made
GitHub	Pick the repository (needs the Plotter GitHub app, in Team settings › Integrations)	None: previews come from whatever reports deployments to GitHub, such as Vercel, Netlify or a workflow

If something goes wrong, the source shows why under its address, for example a secret that doesn't match.

Still stuck? A person answers every email, usually the same day.Email hello@plotter.run