Skip to main content

Optionally disable deployment_status webhook events for GitHub Actions

By Steven Van ·

Vercel's GitHub connection can skip per-deployment status events, but Actions workflows that rely on them should move to repository_dispatch.

Teams that connect Vercel to a GitHub repository can now stop it sending the deployment_status webhook event. While the events are enabled, pull request activity gets a log entry with a status event for every deployment. In repositories with many deployments, especially monorepos with many projects, that makes the event history noisy. Turning the events off keeps repeated messages out of the PR's history.

The Vercel GitHub comment with links to preview deployments is unaffected and is posted as before. Anyone who uses deployment_status as a trigger for GitHub Actions should check their workflows first, since that is the event's most common use. Vercel recommends migrating those workflows to repository_dispatch events, which it says are simpler and carry richer Vercel deployment information.

Vercel
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →

Original source

Read Optionally disable deployment_status webhook events for GitHub Actions on Creators Toolbox