Vercel CI can now run on GitHub repositories without a linked Vercel project
Vercel CI can now run on a GitHub repository that has no Vercel project, removing the need to create an empty project to connect the repository. Support is limited to private GitHub repositories; public repositories and other Git providers are not yet supported.
Why it matters
Teams can adopt Vercel CI for private GitHub repositories without creating placeholder Vercel projects, which simplifies setup for repositories that are not deployed to Vercel.
Who should care
Developers and engineering teams using private GitHub repositories with Vercel CI, especially teams running CI tasks without deploying to Vercel.
What you can do
Confirm the Vercel GitHub App is installed with access to a private repository, ensure you have write or admin permission on it, and enable Vercel CI from a clone of the repository using the Vercel CLI.