[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Feedback](/c/feedback/8) # Require verified commits setting not respected in Vercel 45 views · 1 like · 8 posts Roger W (@rogerwillcocks-9993) · 2026-01-26  } Anshuman Bhardwaj (@anshumanb) · 2026-01-27 Hi @username, I acknowledge your concern regarding the verified commits setting in Vercel. To assist you effectively, could you please provide the following details: 1. A description of the verified commits setting you are referring to. 2. Any specific error messages or logs related to this issue. Let me know if you need more details. Roger W (@rogerwillcocks-9993) · 2026-01-27 In the screenshots #1 shows the settings from the Vercel UI for the project. #2 is the failure message Vercel is posting to GitHub. Anshuman Bhardwaj (@anshumanb) · 2026-01-27 Hi @rogerwillcocks-9993, is this a public repository? If not, Vercel GitHub integration requires the commit from Vercel account to initiate deployments. **For Public Repositories:** You can deploy from public repositories on any plan level, including the Hobby (free) plan. However, on Hobby, only the account owner can trigger deployments - the commit author must be the owner of the Hobby team. **For Private Repositories:** You need a Pro plan to deploy from private repositories in GitHub organizations. The Hobby plan does not support deploying from private repositories in GitHub organizations. Here's the key difference: * **Hobby Plan**: Cannot deploy from private repositories in GitHub organizations, GitLab groups, or Bitbucket workspaces. You'd need to either make the repository public or upgrade to Pro. * **Pro Plan**: Supports private repository deployments with team collaboration. Each person committing code (and creating pull requests) needs to be added as a member of your Vercel team, and they should link their GitHub account to their Vercel account. On Pro teams, when someone creates a pull request, Vercel verifies they're a team member. If they're not, the deployment is prevented, and they can request to join the team. I hope this clarifies your doubt. Roger W (@rogerwillcocks-9993) · 2026-01-27 · ♥ 1 It’s private, and we have Pro. We have all the options in the Vercel UI **turned off** for GtiHub integration The only reason we have integration turned on at all is because it is required to enable branch specific environment variable settings for our projects. We **push** builds based on our criteria. Anshuman Bhardwaj (@anshumanb) · 2026-01-28 I understand that but is the commit author from the error message part of your Vercel Pro team? Roger W (@rogerwillcocks-9993) · 2026-01-28 Ah. No, it seemed to be the GitHub Agent carrying out a merge to bring a branch up to date. Pauline P. Narvas (@pawlean) · 2026-01-28 Could this be related? https://community.vercel.com/t/a-commit-author-is-required-when-git-is-properly-configured/23724/4?u=pawlean