Technology1 min read

Vercel CI no longer requires a linked Vercel project

By · Published by Everything Blog

In short

Continuous integration can now operate independently without creating an empty deployment project just to establish a connection. Users need write or admin access, linked GitHub and Vercel accounts, and the official Vercel GitHub App installed. Running the "vercel ci enable" command triggers workflows to run automatically on subsequent git pushes. However, this workflow is presently restricted to private GitHub repositories.

Key points

  • Workflows trigger and execute tasks automatically as soon as a new commit is pushed to th…: Workflows trigger and execute tasks automatically as soon as a new commit is pushed to the repository.
  • A scope flag is available in the CLI to route the continuous integration setup to a diffe…: A scope flag is available in the CLI to route the continuous integration setup to a different team.
  • Support is currently restricted to private GitHub repositories, leaving out public repos…: Support is currently restricted to private GitHub repositories, leaving out public repos and alternative Git hosting providers.

Sources checked by our analysis pipeline: 1

Vercel CI can now run on a GitHub repository that has no Vercel project. Until now you had to create an empty project just to connect the repository.

To enable it, you need:

The Vercel GitHub App installed with access to the repository

Your GitHub account connected to your Vercel account

Write or admin permission on the repository

Then, from a clone of the repository, run:

vercel ci enable

CI is enabled for the team your CLI is set to. Pass --scope <team>

to use a different one. From the next push, tasks run as configured in your repository.

Private GitHub repositories only. Public repositories and other Git providers are not yet supported.

Read the Vercel CI documentation to configure tasks.

Technology