GitHub push events stopped triggering builds on both projects — Hobby plan

Help
1

Both of my Vercel projects have stopped auto-deploying from GitHub pushes. The pipeline was working perfectly for months, then stopped after a specific commit with no configuration changes on my end.
Symptoms:

  • Pushes to master generate zero deployments — not even failed/cancelled ones
  • Deploy hooks return {"job":{"state":"PENDING"}} but no deployment ever appears
  • Manual “Redeploy” from the dashboard works fine (reuses cached artifacts)
  • Both projects show as “Connected” to GitHub in Git settings
  • GitHub App is installed with “All repositories” access
    What I’ve tried:
  • Disconnecting and reconnecting the GitHub integration on both projects
  • Multiple empty commits to force push events
  • Posting to deploy hook URLs directly
    The pattern: The Vercel API shows a clean cutoff — every commit before a certain point has a deployment, every commit after has none. 9 pushes across both projects, zero deployments created.
    This looks like something broken in Vercel’s internal webhook processing for my account rather than a configuration issue. Is there any way the team can check internal event logs?
2

Hi Brian,

Since manual redeploys work but Git pushes and Deploy Hooks create no visible deployments, I’d check the settings that can stop deployment creation before digging into build logs.

A few quick checks:

Project Settings → Git
- Is the production branch still `master`?
- Are ignored build step settings enabled?
- Is the repo connected to the same GitHub repo/branch you are pushing to?

I’d also search the repo for Git deployment-disabling config:

grep -R "deploymentEnabled\|github.*enabled" vercel.json vercel.ts . 2>/dev/null

If you have either of these, they can prevent Git-triggered deployments:

{
  "git": {
    "deploymentEnabled": false
  }
}

or the older form:

{
  "github": {
    "enabled": false
  }
}

One more useful separation test: create a brand new Deploy Hook for the exact branch you expect, then trigger that new hook once with curl. If the new hook also returns PENDING but no deployment appears, and Git pushes also create nothing across both projects, that is strong evidence to include in a support case because it suggests the trigger is not making it into deployment creation at all.

I would not rotate or post the deploy hook URLs publicly, since they work like trigger secrets.