Hi Vercel team,
I recently experienced a frustrating issue where my deployments were blocked because a Git author wasn’t connected to Vercel, even though I had already linked my GitHub account.
As a Hobby plan user managing multiple projects, this policy created unnecessary friction. Here’s my feedback:
-
The blocking feels too aggressive — Even as the account owner, I was unable to deploy my own code without additional verification steps.
-
Multi-author workflows are common — Many solo developers work across different machines or have varied Git configurations. Requiring every commit author to be connected to Vercel adds complexity that feels out of proportion to the risk.
-
Clearer guidance would help — When blocked, the error messaging didn’t make it immediately obvious how to resolve the issue.
Suggestion: Consider making this an opt-in security feature rather than a hard block, or provide a smoother path to override for account owners who understand the risks.
I love using Vercel for its speed and simplicity, but experiences like this make me consider alternatives. I hope this feedback helps improve the platform for other Hobby users.
kindly consider this at highest priority or loose us (students or hobbyist)
Thanks for listening.