Using Git with Vercel provides the following benefits:
- Preview Deployments for every push.
- Production Deployments for the most recent changes from the Production Branch.
- Instant rollbacks when reverting changes assigned to a custom domain.
The easiest way to use Git is to think of your
main branch as production. Every time a pull/merge request is made to that branch, Vercel will create a unique deployment, allowing you to view the changes in a preview environment before merging.
In this case,
main is the Production Branch. When merging to the Production Branch, a Production Deployment is made, making the latest changes available to assigned custom domains automatically.
You can choose to use a different branch as the Production Branch.
Setting up your GitHub, GitLab, or Bitbucket repository on Vercel is only a matter of clicking the "New Project" button on the top right of your dashboard and following the steps.
After clicking it, you'll be presented with a list of Git repositories that the Git account you've signed up with has write access to.
To select a different Git namespace or provider, you can use the selector on the top left of the section.
Alternatively, you can also:
- Select a third-party Git repository by clicking on "Import Third-Party Git Repository" on the bottom of the section.
- Select one of our pre-built templates from the section on the right.
After you've selected the Git repository or template you want to use for your new project, you will be presented with a list of Personal Vercel Accounts and Vercel Teams you can deploy it to.
After having made your choice, click "Continue".
If you've selected a Git repository that you have write access to, you're all set and the next page will let you create a new Project and deploy your code.
If you've selected a third-party Git repository or template, however, a different page will invite you to create a new Git repository. The third-party Git repository or template will then be cloned there.
Once the Project has been created, you will be redirected to the Project's page on your dashboard. Congratulations!
In order to deploy commits from a private Git Repository (or a fork of a private Git Repository) under a Team, the commit author has to be a member of the Team on Vercel (even if the commit author is a bot).
If the commit author is not a member, the Deployment will be prevented and a request to join the Team can be issued by the commit author. After that, the owners of the Team will be notified and can either accept or decline the membership request on the "Members" page in the Team Settings.
Declining the request will leave the commit undeployed. If the commit author gets accepted as a member of the Team, however, their most recent commit will resume to be deployed to Vercel automatically.
Commit authors will automatically be considered a part of the Team on Vercel if one of the existing members connected their Personal Account on Vercel with the Git account that created the commit.
When you receive a pull request from a fork of your repository that includes a change to the
vercel.json file or the Project has Environment Variables, Vercel will require authorization from you or a member of your Team to deploy the pull request.
This behavior protects you from leaking sensitive Project information.
You can disable Git Fork Protection in the Security section of your Project Settings.
When a public repository is forked, commits from it will usually deploy automatically. However, if the
vercel.json file changed, an owner of the Project on Vercel has to authorize the Deployment. This is a security measurment that ensures changes to environment variables and other configuration properties are reviewed before a Deployment is created. A link to authorize the Deployment will be posted as a comment on the Pull Request.
The authorization step will be skipped if the commit author is already a member of the Team on Vercel.
A Production Deployment will be created each time you merge to the Production Branch.
When you create a new Project from a Git repository on Vercel, the Production Branch will be selected in the following order:
- If not present, the
masterbranch (more details).
- [Only for Bitbucket] If not present, the "Production Branch" setting of your Git repository is used.
- If not present, the Git repository's default branch.
On the Git page in the Project Settings, you can change your Production Branch.
Whenever a new commit is then pushed to the branch you configured here, a Production Deployment will be created for you.
While the Production Branch (mentioned above) is a single Git branch that contains the code that is served to your visitors, Preview Branches are all the Git branches that are not the Production Branch.
For example, if your Production Branch is
main, then all the Git branches that are not
main are considered Preview Branches. That means there can be many Preview Branches, but only a single Production Branch.
Preview Branches, like the name already suggests, are used for previewing changes before presenting them to your visitors (merging them into Production).
By default, every Preview Branch automatically receives its own Domain similar to the one shown below, whenever a commit is pushed to it:
Additionally, any Environment Variables defined for the Preview Environment are applied.
Once you're happy with your changes, you would then merge the respective Preview Branch into your Production Branch.
For most use cases, the default Preview behavior mentioned above is enough.
If you'd like your changes to pass through multiple phases of previewing instead of just one, you can accomplish it like so:
For example, you could create a phase called "Staging" where you can accumulate Preview changes before merging them onto Production by following these steps:
- Create a Git branch called "staging" in your Git repository.
- Add a Domain of your choice (like "staging.example.com") on your Vercel project and assign it to the "staging" Git branch like this.
- Add Environment Variables that you'd like to use for your new Staging phase on your Vercel project like this.
Afterwards, you can push to the "staging" Git branch to update your Staging phase and it will automatically receive the Domain and Environment Variables you've defined.
Once you're happy with your changes, you would then merge the respective Preview Branch into your Production Branch. However, unlike with the default Preview behavior, you'd then keep the branch around instead of deleting it, so that you can push to it again in the future.
If you'd like to deploy multiple different directories within the same Git repository, you can do so by creating a separate Project for each directory and configuring the Root Directory setting for it.
The easiest way to achieve this is by importing your Git repository multiple times and selecting a different Root Directory every time – until one Project was created for each of the relevant directories.
Once you've created a separate Project for each of the directories within your Git repository, every commit will issue a Deployment for all connected Projects and display the resulting URLs on your pull requests and commits:
Because it's only possible to link a single Vercel Project when running the
vercel command, we recommend cloning your Git repository multiple times and then running
vercel for each one to deploy them.
The same applies to the
vercel dev command (local Development).
In the future, this workflow piece will be improved drastically. In the meantime, we strongly suggest using Git instead of Vercel CLI.
Pushing a commit to your monorepo will create a Deployment for each of the connected Vercel projects.
If you want to abort the Build Step for certain projects if their files didn't change, you can do so with the Ignored Build Step project setting.