Require verified commits setting not respected in Vercel

Feedback
, ,
1

image
image1770×515 35.7 KB

image
image1205×114 16.2 KB
}

5

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.

6

In the screenshots

#1 shows the settings from the Vercel UI for the project.

#2 is the failure message Vercel is posting to GitHub.

7

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.