# Optionally disable deployment\_status webhook events for GitHub Actions

**Published:** May 1, 2025 | **Authors:** Erika Rowland, Tom Knickman

---

You can now disable the [`deployment_status` webhook event](https://docs.github.com/en/webhooks/webhook-events-and-payloads#deployment_status) that Vercel sends to GitHub when Vercel is connected to your GitHub repository.

When `deployment_status` events are enabled, GitHub's pull request activity will create a log with a status event for every deployment. While this can keep your team better informed, it can also create noisy event logs for repositories with many deployment events, especially in monorepos with many projects.

![deployment_status changes (light)](//images.ctfassets.net/e5382hct74si/3pczJCHM1o1D9hyJmsQZPP/e743fc5b23b9be5eadbafef7deef442b/Changelog_Image_752__1_.png)

Disabling these events prevents repeated messages from cluttering your GitHub PR's event history, giving you a cleaner, more focused view of your pull request activity. The Vercel Github comment containing links to your preview deployments will continue to be posted as before.

![deployment_status events GONE (light)](//images.ctfassets.net/e5382hct74si/6Whhz8vnOnvj9D9mVZ1XW0/5b39f22344f5cda59260333b4969d6a4/Changelog_Image_753__1_.png)

The [`deployment_status` event](https://docs.github.com/en/rest/deployments/deployments?apiVersion=2022-11-28) is most often used as a trigger for GitHub Actions. We recommend [migrating to `repository_dispatch` events](https://vercel.com/docs/git/vercel-for-github#migrating-from-deployment_status) to simply workflows with richer Vercel deployment information.

[Learn more in the documentation](https://vercel.com/docs/git/vercel-for-github#silence-deployment-notifications-on-pull-requests).

---

📚 **More updates:** [View all changelog entries](/changelog/sitemap.md) | [Blog](/blog/sitemap.md)