Connecting Git Repositories at the Project Level
Vercel has updated how projects interact with Git accounts, particularly benefiting larger teams and agencies. Git connections are now scoped per project rather than per account. This change allows users to associate multiple GitHub, GitLab, or Bitbucket connections with a single Vercel account, with different connections applied to different projects.
This means a Git namespace—such as a GitHub account or organization—can be linked to an individual project. Each project can maintain its own distinct Git connection, decoupling repository access from a single account-wide setting.
A Faster Path from Repository to Deployment
The project creation flow has been redesigned to shorten the time between import and deployment. When creating a new project, you can now search directly for existing repositories from the initial creation screen. This change reduces the number of page loads required during the import process, streamlining the setup sequence.
The Git integration component within the creation phase is interactive, allowing you to connect a repository or start from a template immediately.
Templates and Advanced Next.js Starters
For those starting without an existing repository, the template library has been integrated directly into the project creation flow. This approach lets you reuse pre-built components and pages to cut down on initial development time.
Two advanced Next.js templates have been added to the library: Next.js Commerce and Virtual Event Starter Kit. Both include a range of sophisticated components and pages that can be cloned and customized. They can be found under "Browse All Templates" within the "Clone Template" container. These updates apply to all users across Hobby, Pro, and Enterprise plans.
