DEV Community

Cover image for My Vercel deployment was "Blocked": the culprit was the email on my commits
Amine Affif
Amine Affif

Posted on

My Vercel deployment was "Blocked": the culprit was the email on my commits

#vercel #git #devops #webdev

I push to main, Vercel starts a deployment, and it sits in Blocked. No build error, no logs. Just this reason:

The deployment was blocked because the commit author doesn't have
permission to create deployments for this project.
Enter fullscreen mode Exit fullscreen mode

My first reflex was to redeploy from the CLI with vercel --prod. Same result. The CLI attaches the latest commit's metadata to the deployment, so it inherits the same block.

The cause: the commit author's email address. It wasn't linked to any GitHub account with access to the Vercel project. The code had nothing to do with it.

To check:

git log --format='%h %an <%ae>' -3
Enter fullscreen mode Exit fullscreen mode

The fix: sign commits with the address linked to your account, then push an empty commit to trigger again.

git -c user.email="your-address@example.com" commit --allow-empty -m "Retrigger deployment"
git push
Enter fullscreen mode Exit fullscreen mode

The deployment went through in 34 seconds.

One tip: in a personal repo, set the address once with git config user.email, so you don't depend on your machine's global configuration.

Amine Affif, full-stack developer in Paris. amineaffif.com

Top comments (0)

Some comments may only be visible to logged-in visitors. Sign in to view all comments.