[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Urgent: GitHub Webhook failing and "A commit author is required" bug on manual deploy

19 views · 0 likes · 2 posts


Aymn_idm (@zwarthand2006-4121) · 2026-02-20

Hello Vercel Support Team,

I am experiencing a critical issue with my repository connection. My Vercel project is successfully linked to my GitHub repository (GhostNight13/haiskills), and it shows as “Connected” in the project Git settings. However, Vercel is completely ignoring all new commits pushed to the main branch. The last successful automatic deployment was on February 12th.

To troubleshoot, I attempted to trigger a deployment manually via the Vercel Dashboard (“Create Deployment” using the main branch and specific commit SHAs). Every manual attempt fails instantly with the UI error:

“A commit author is required”

I have already tried the following troubleshooting steps without success:

1. Disconnecting the Git repository in my Vercel project settings and reconnecting it.
2. 2. Revoking Vercel’s OAuth access entirely on GitHub and doing a fresh clean re-authentication.
   3. 3. Granting the Vercel GitHub App access to “All repositories” instead of just the specific project.
   4. Despite these steps, the webhook remains dead and manual deployments refuse to start due to the missing commit author metadata error. Could you please investigate my account / project (haiskills) to clear any stuck Git cache or restore the missing GitHub API permissions on your backend?
3. Thank you for your assistance.


Amy Egan (@amyegan) · 2026-02-23

"A commit author is required" usually means there's a problem with commit metadata. Linking an article with metadata setup instructions. Can you give that a try and let me know whether that solves it?

[https://vercel.com/kb/guide/why-aren-t-commits-triggering-deployments-on-vercel#correctly-configured-metadata](https://vercel.com/kb/guide/why-aren-t-commits-triggering-deployments-on-vercel#correctly-configured-metadata)