Hello,

A GitHub pull request was merged into our production branch (main), but no Vercel deployment was created for the merge commit.

The existing production deployment remains available; this is a blocked release, not an outage.

What happened

• The PR’s latest commit successfully received a Preview deployment.
• The PR was merged into main on November 9, 2026, at 11:05:03 UTC.
• After the merge, there was no deployment record for the merge SHA and no Vercel commit status on GitHub.
• Another project on the same Vercel team successfully deployed its merge during the same release session.

What we checked

• The correct GitHub repository is connected.
• The Production environment tracks main.
• Ignored Build Step is set to Automatic.
• Skipping deployments for unaffected projects is disabled.
• There is no vercel.json, vercel.toml, or vercel.ts in the merged tree.
• The merge commit is verified, associated with the repository owner’s GitHub account, and contains no skip marker.
• No relevant incident was listed on the Vercel status page.

We have not disconnected the Git integration, changed settings, or manually triggered a deployment, to preserve the current state for diagnosis.

The support assistant indicated that internal webhook delivery or ingestion logs would be needed, but the case form directed our Hobby account to the community.

Is there a way to determine whether Vercel received this specific GitHub event and why it did not create a deployment? If staff can investigate, we can provide the project ID and full commit SHA through an appropriate private channel.

We would appreciate guidance on diagnosis before trying a reconnect or manually triggering a deployment.

Thank you.