Hello Vercel Community,
I'm experiencing an issue where a GitHub push succeeds, but Vercel does not create an automatic Preview deployment. There is no failed, skipped, ignored, or queued deployment event.
Environment
- Plan: Hobby
- Framework: Next.js 16.2.9
- Repository: Private GitHub monorepo (pnpm workspace)
- Vercel Root Directory:
apps/web - Build Command:
pnpm build - Git deployment creation: Enabled
- Ignored Build Step: Not configured
- Skip Unaffected Projects: Enabled
What happened
The previous commit on the same branch successfully triggered a Preview deployment.
Previous commit:
98d0cd88019023169d29b4e73148ffb4d6d7fa00
Target commit:
a5756983db7858821d8ea2f81b6a1e4394ed271e
The target commit was successfully pushed to GitHub, but Vercel did not create a deployment.
Both changed files are located directly inside the configured Root Directory:
apps/web/scripts/verify-preview-database-targets.tsapps/web/scripts/verify-preview-database-targets.test.ts
What I've verified
- The remote GitHub branch points to the target commit.
- GitHub reports zero check runs and zero commit statuses.
- Vercel reports zero deployments for the target SHA.
- No deployment event appears in Vercel Activity.
- The Vercel GitHub App is installed, active, and has access to the repository.
- Automatic Git deployments are enabled.
- Both changed files belong to the affected web project.
- Production remains healthy and unchanged.
Commit author identity
Both the successfully deployed commit and the missing deployment commit have exactly the same Git author and committer email.
GitHub attributes both commits to the same account, while the Vercel account has a different GitHub login connection. However, the previous commit deployed successfully with this identical author identity.
Questions
- Can the Hobby plan's commit-author identity validation silently prevent a Preview deployment without creating a GitHub check or Vercel Activity event?
- Could a GitHub App push event fail to be processed even though the repository integration remains connected?
- Is there a safe way to retry processing this exact commit without reconnecting the integration, changing Git history, or affecting Production?
I would appreciate any guidance from Vercel staff or community members who have encountered this behavior.
Thank you!