Deploying to Vercel from Any GitHub Account on the Hobby Plan

Deploying to Vercel from Any GitHub Account on the Hobby Plan

If you’re on Vercel’s free Hobby plan and collaborate with others (or use bot accounts like Claude), you’ve probably hit this error:

Git author 5108979+someuser@users.noreply.github.com must have access to the team on Vercel to create deployments.

Vercel checks the git commit author against team members. On the Hobby plan, there’s only one member: you. So commits authored by anyone else — a collaborator, a CI bot, an AI coding assistant — get rejected at deploy time.

Why This Happens

When you run vercel deploy --prebuilt in a GitHub Actions workflow, the Vercel CLI reads git metadata from the checked-out commit. It sees the commit author’s email and checks whether that person is a member of the Vercel team that owns the project.

On the Pro plan, you’d just add collaborators to your team. On the Hobby plan, there’s exactly one seat — the account owner. Every other git author gets rejected.

This is especially painful if you’re using AI coding tools that commit under their own identity, or if you have a shared repo where multiple people push commits that trigger deployments.

The Fix: Amend the Commit Author in CI

GitHub Actions checks out code into an ephemeral runner. You can amend the commit there without affecting your actual git history. Just rewrite the author to match the Vercel account owner before deploying:

- name: Checkout code
  uses: actions/checkout@v4

- name: Set Vercel-compatible git author
  run: |
    git config user.email "your-vercel-email@example.com"
    git config user.name "your-vercel-username"
    git commit --amend --no-edit --reset-author

That’s it. --reset-author rewrites the commit’s author to match the current git config. --no-edit keeps the commit message unchanged. Your actual repository history is untouched — this only affects the disposable CI checkout.

Place this step right after checkout, before anything else runs. The rest of your workflow — vercel pull, vercel build, vercel deploy — proceeds as normal, and Vercel sees a commit authored by the account owner.

The Full Workflow

  name: Vercel Deploy
  
  on:
    push:
      branches:
        - "**"
  
  env:
    VERCEL_ORG_ID: $
    VERCEL_PROJECT_ID: $
  
  jobs:
    deploy:
      runs-on: ubuntu-latest
  
      steps:
        - name: Checkout code
          uses: actions/checkout@v4
  
        - name: Set Vercel-compatible git author
          run: |
            git config user.email "your-vercel-email@example.com"
            git config user.name "your-vercel-username"
            git commit --amend --no-edit --reset-author
  
        - name: Setup Node.js
          uses: actions/setup-node@v4
          with:
            node-version: 20
            cache: npm
  
        - name: Install dependencies
          run: npm ci
  
        - name: Pull Vercel environment
          run: npx vercel pull --yes --token=$
  
        - name: Build
          run: npx vercel build --token=$
  
        - name: Deploy
          run: npx vercel deploy --prebuilt --token=$

Why Not Just Upgrade?

Vercel’s Pro plan ($20/month per member) solves this by letting you add team members. But if you’re an indie developer working with AI coding assistants or occasional collaborators, paying per-seat for what amounts to a git metadata check feels wrong. The commit author amend is a clean workaround. It doesn’t forge history, doesn’t require shared credentials, and works with any number of contributors pushing to the repo. The VERCEL_TOKEN handles authentication — the git author is just a metadata check that happens to block Hobby plan deployments from non-owner commits.

If you’re building CI/CD pipelines for side projects and running into similar platform quirks, find me on Twitter at @karancito.