# Optionally disable deployment\_status webhook events for GitHub Actions

By Steven Van · 2025-05-01

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](<https://creatorstoolbox.com/tools/vercel>) to a GitHub repository can now stop it sending the [deployment\_status webhook event](<https://docs.github.com/en/webhooks/webhook-events-and-payloads#deployment_status>). 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](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

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

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://docs.github.com/en/webhooks/webhook-events-and-payloads#deployment_status>)

[Read Optionally disable deployment\_status webhook events for GitHub Actions on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-optionally-disable-deployment-status-webhook-events-for-github-actions>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-optionally-disable-deployment-status-webhook-events-for-github-actions