Both projects stopped creating deployments on push to main simultaneously, at commit 3425b561f93477cb3544b5f5481706bc7f49fa9e, with no error. Every push since has produced zero new deployments on either project — not even failed ones.

Concrete reproduction (new finding): GET /v9/projects/prj_l3CBzXpuReNfNd8omX1GQxgBQAyz returns a link object showing the connection as correct: "link": { "type": "github", "repo": "auction-platform", "repoId": 1261123315, "org": "EliteFix", "productionBranch": "main", "gitCredentialId": "cred_4b56618b863c986a19a498a79632b8095d79fd09", "deployHooks": [ ] } But calling POST /v1/projects/prj_l3CBzXpuReNfNd8omX1GQxgBQAyz/deploy-hooks with {"name":"test","ref":"main"} returns: {"error":{"code":"git_branch_not_found","message":"Branch "main" not found in the connected Git repository."}} i.e., Vercel's backend can't resolve the exact branch its own project config names as the production branch. This would explain why GitHub push events produce nothing — the credential (gitCredentialId above) tied to this connection appears unable to actually read branch data from GitHub, despite the project believing it's connected.

Steps already taken (all unsuccessful):

1. Confirmed each push reached GitHub (git ls-remote matches main).
2. Disconnected/reconnected Git integration via the dashboard.
3. Confirmed on GitHub ( github.com/settings/installations ) the Vercel GitHub App has explicit access to the repo.
4. vercel git connect --yes — initially failed with Failed to connect ... make sure you have access, later (after a team-level Git re-auth) reported already connected.
5. Fully uninstalled and reinstalled the Vercel GitHub App on GitHub, re-granting repo access — no change.
6. Multiple test pushes after every step above — zero deployments each time.
7. Confirmed via direct API call that creating a deploy hook for the project's own productionBranch ("main") fails with git_branch_not_found.

Current workaround: deploying manually via vercel deploy --prod from a local clone — these succeed normally, confirming build config/env vars are fine; the break is isolated to Vercel's GitHub branch/webhook resolution for this connection.

Ask: the gitCredentialId on this connection (cred_4b56618b863c986a19a498a79632b8095d79fd09) appears to be unable to resolve branches on the connected repo — please check/refresh it server-side, or advise if it needs to be fully re-provisioned.

Hi EliteFix,

This repro is useful because vercel deploy --prod and Git-triggered deployments use different paths. The CLI deploy succeeding means the build settings/env are probably fine, but it does not prove the GitHub App credential used for automatic deployments can still read the repo refs.

The strongest clue is this part:

1
git_branch_not_found
2
Branch "main" not found in the connected Git repository.
3

If Vercel’s project link says the production branch is main, but Vercel cannot create a deploy hook for main, I’d focus on Git connection metadata rather than Next.js or build config.

One test I’d try is importing the same GitHub repo into a brand-new temporary Vercel project from the dashboard, using the same team and GitHub App installation.

If the new project can see main and deploy on push, the old project’s Git link/credential is probably stale. If the new project also cannot see main, the issue is more likely at the GitHub App installation/org permission layer.

I’d also remove the project ID and gitCredentialId from the public post. They are not API keys, but they are still internal identifiers and do not need to be public.