(edited)
}
⌘K
}
Hi , I acknowledge your concern regarding the verified commits setting in Vercel. To assist you effectively, could you please provide the following details:
Let me know if you need more details.
In the screenshots
#1 shows the settings from the Vercel UI for the project.
#2 is the failure message Vercel is posting to GitHub.
Hi , 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:
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.
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.
I understand that but is the commit author from the error message part of your Vercel Pro team?
Ah.
No, it seemed to be the GitHub Agent carrying out a merge to bring a branch up to date.
