Deployments blocked-Contributor Access incorrectly resolving GitHub identity to wrong Vercel account

Help
1

Hi,

I’m experiencing an issue where my deployments are being blocked due to the Contributor Access feature incorrectly resolving my Git identity to the wrong Vercel account.

Setup:

  • I have two Vercel accounts: xxx-9861 (for this project) and zzz-1045 (for a separate business)

  • My GitHub account (primary email: xxx@gmail.com) is connected to both Vercel accounts

  • I am trying to deploy to a project owned by xxx-9861

Problem: When I push commits or deploy via CLI, Vercel resolves my Git identity to xxx-1045 instead of xxx-9861, even though:

  • I am logged into Vercel CLI as xxx-9861 (confirmed via vercel whoami)

  • The project belongs to xxx-9861

  • My GitHub email is verified and set as primary

Error messages:

  1. Git deployments: “The deployment was blocked because the commit email xxx@gmail.com could not be matched to a GitHub account. Ensure your git email matches your GitHub account.”

  2. CLI deployments (vercel deploy): “Error: Unexpected error. Please try again later.”

What I’ve tried:

  • Confirmed I’m logged into the correct Vercel account via CLI

  • Verified my email is primary and verified on GitHub

  • Attempted deploying via both Git push and vercel deploy command

This issue started after the new permissions/Contributor Access feature was implemented. Previously, deployments worked without issue using the same Git account and credentials.

This appears to be a bug in how Contributor Access resolves identity when a GitHub account is connected to multiple Vercel accounts. The system should resolve to the account that owns the project being deployed to.

Any help would be appreciated!