Why aren't commits triggering deployments on Vercel?

You've been working on a feature and have committed some code ready to be pushed up. You're looking forward to a live URL that demonstrates your changes. You see that the commit has been pushed up, but there isn't an accompanying deployment on Vercel to match. Read on to learn about why this might happen and what you can do to fix it.

Doublecheck Git Integration Installation

When you installed the Vercel for Git integration, if you only granted permission for a limited set of repositories, there is a chance that the repository you are trying to push to doesn't have the necessary permissions. You can resolve this from the Git provider side by either granting permissions for all of your repositories, or you can make sure the repository in question is added to the list.

Team Seats

If you are deploying to a repository connected to a Vercel project that belongs to a team, you need to make sure that you are a member of that Vercel team, or else your commits will require approval from a team owner. Once you've been added to the team, your commits will get deployed as expected.

Correctly Configured Metadata

In order for your commits to get registered properly with your Git account, you need to make sure your commit author information is appropriately configured locally. If your email does not match up with your GitHub, GitLab, or Bitbucket account, there is no way to verify that your commits are authorized for deployment.

The commands for configuring your name and email are shown below:

git config --global user.name "John Doe"
git config --global user.email johndoe@example.com

Shell commands for configuring your Git commit author metadata.

Look For Commit Comments

If the Vercel for Git integration is installed properly, the Vercel Bot will leave comments on your commits that indicate success or failure. These comments may not always be present on the pull request if no deployment could be created, this occurs when pre-deployment validation fails, for example, an incorrectly formed vercel.json file.

Deduplicated Builds

If you're merging to your production branch from a preview branch and there are no new environment variables associated with each respective branch, the deployment from your preview branch will be promoted to production without triggering a new build. This is done for efficiency since re-buidling your project will make no difference for the final output. The full criteria for when builds are deduplicated can be found here

Vercel Support

If after considering all of the above, you're still having issues. Please email support@vercel.com with the most recent git SHA in question.

Updated October 16th 2020