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.
When working with Git, have a branch that works as your production branch, often called
main. After you create a pull request (PR) to that branch, Vercel creates a unique deployment you can use to preview any changes. Once you are happy with the changes, you can merge your PR into the
main branch, and
Vercel will create a production deployment.
You can choose to use a different branch as the Production Branch.
- GitHub Free
- GitHub Team
- GitHub Enterprise Cloud
- GitHub Enterprise Server
- GitLab Free
- GitLab Premium
- GitLab Ultimate
- GitLab Enterprise
- Self-Managed GitLab
- Bitbucket Free
- Bitbucket Standard
- Bitbucket Premium
- Bitbucket Data Center (Self-Hosted)
- Azure DevOps Pipelines
If your provider is not listed here, you can also use the Vercel CLI to deploy with any git provider.
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 dropdown list on the top left of the section.
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'll be taken to a page where you can configure your project before it's deployed.
- Customize the project's name
- Select a Framework Preset
- Select the root directory of your project
- Configure Build Output Settings
- Set Environment Variables
When your settings are correct, you can select the Deploy button to initiate a deployment.
As an additional security measure, commits on private Git repositories (and commits of forks that are targeting those Git repositories) will only be deployed if the commit author also has access to the respective project on Vercel.
Depending on whether the owner of the connected Vercel project is a Personal Account or a Team, the behavior changes as mentioned in the sections below.
This only applies to commit authors on GitHub organizations, GitLab groups and non-personal Bitbucket workspaces. It does not apply to collaborators on personal Git accounts.
For public Git repositories, a different behavior applies.
In order to deploy commits under a Vercel Team, the commit author must be a member of the Team that contains the Vercel project that is connected to the Git repository.
The membership is checked by finding the Personal Account associated with the commit author through comparing Login Connections, and then, if a Personal Account is found, checking if it is a member of the Team.
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.
In order to deploy commits under a Personal Vercel Account, the commit author must be the owner of the Personal Account that contains the Vercel project that is connected to the Git repository. This is determined through comparing the Login Connections defined in the Personal Account with the commit author.
For cases in which the commit author is not the owner of the destination Personal Account, the Deployment will be prevented and a recommendation for transferring the project to a Vercel Team will be displayed on the Git provider.
After having transferred the project to a Vercel Team, commit authors can easily be added as members of that Team and will see the behavior mentioned in the section above applied for them whenever they commit.
When a public repository is forked, commits from it will usually deploy automatically. However, 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 Team Member to deploy the pull request. This is a security measure that protects you from leaking sensitive project information. 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 Team Member 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.
You can also receive feedback from team members and other collaborators through Vercel's Comments feature. Comments can be tracked and resolved from within a PR on GitHub.
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.