New Commits to main Do Not Trigger Deployments

Help
1

Hi everyone,
I’m having an issue where Vercel is not detecting any of my new commits on the main branch, even though my project is fully connected to GitHub.

What’s happening

  • My production deployment keeps showing the initial commit (9a79e7a) as the source.

  • My latest commit is 2a1ce67, and it’s in the main branch on GitHub.

  • Pushing new commits to main does not trigger a new deployment in Vercel.

  • The “Deployments” tab shows no new builds since the first one.

What I’ve already done

  1. Confirmed my GitHub repo is connected (Vercel → Project → Git).

  2. Reinstalled the Vercel GitHub App and granted full repo access again.

  3. Verified GitHub shows the Vercel GitHub App with correct permissions.

  4. Checked GitHub webhooks — no manual webhooks exist (as expected).

  5. Created a Deploy Hook on Vercel (but I know this is separate from GitHub triggers).

  6. Tried a manual redeploy, but Vercel redeploys the old commit only.

  7. Confirmed:

    • Production branch = main

    • Repo name hasn’t changed

    • Branch protection isn’t blocking pushes

    • Commits show up correctly in GitHub

What I’m trying to understand

Why is Vercel still stuck on the initial commit and not seeing any GitHub updates, even though my repository is connected and the GitHub App is installed correctly?

Any insight on what might be causing Vercel to ignore new commits to the production branch would be greatly appreciated.

Thanks in advance!

3

I have read this Why aren't commits triggering deployments on Vercel? | Knowledge Base

4

I realized that my git config wasn’t pointing to my username or email! That solved the problem.

1 Like
6

I’m glad you figured it out. Thanks for sharing your solution here.