Allison is coding...

Addressing Vercel Deployment Issues for Non-Team Members

This guide outlines how to resolve the Vercel deployment error “No access to create deployments” when a GitHub account attempts to deploy to a project owned by a different Vercel team member or a project not configured for multi-account deployment. This typically occurs when a hobby plan user attempts to deploy from a GitHub account not directly linked to the Vercel team, after Vercel fixed a previous bug that allowed this behavior.

The solution involves disabling Vercel’s automatic deployments and utilizing GitHub Actions for deployments instead.

1. Disable Vercel’s Automatic Deployments

Navigate to your GitHub repository. Go to Repository Settings > GitHub Apps > Vercel Config. From there, select either suspend or uninstall to stop Vercel’s automatic build process.

2. Obtain Vercel API Token and IDs

You will need the following information from your Vercel account:

  • VERCEL_TOKEN:
    1. Log in to your Vercel account.
    2. Go to Account Settings > Tokens.
    3. Create a new token and copy its value.
  • VERCEL_ORG_ID:
    1. In your Vercel Account Settings, scroll to the very bottom.
    2. Locate “Vercel ID” and copy its value.
  • VERCEL_PROJECT_ID:
    1. Go to the specific project in Vercel that you are trying to deploy.
    2. Navigate to the project’s Settings.
    3. Find “Project ID” and copy its value.

3. Create GitHub Repository Secrets

In your Hugo project’s GitHub repository:

  1. Go to Settings > Secrets and variables > Actions.
  2. Create three new repository secrets with the exact names below, and paste the corresponding values obtained in the previous step:
    • VERCEL_TOKEN
    • VERCEL_ORG_ID
    • VERCEL_PROJECT_ID

4. Create GitHub Actions Workflow

  1. Visit the official Vercel documentation for using GitHub Actions with Vercel.
  2. Copy the provided workflow template.
  3. In your GitHub repository, create two new workflow files (e.g., in .github/workflows/) and paste the copied content into them.

After completing these steps, your deployments should now be managed by GitHub Actions, resolving the “No access to create deployments” error.