You have been working on a feature and have committed some code ready to be pushed up. You are 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 Vercel Deployment. Read on to learn about why this might happen and what you can do to fix it.
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.
If you are pushing commits to a private repository connected to a Vercel project that belongs to a Team, ensure you are a member of that Vercel Team. Once you have been added to the Team, your commits will deploy as expected.
Learn how to invite others into your team.
Pushed commits will deploy automatically for public repositories. However, if the
vercel.json file changed or the project has Environment Variables, a Team Member on Vercel will have to authorize the Deployment. This is a security measure that ensures changes to Environment Variables and other configuration properties are reviewed before a Deployment is created (it can be disabled if you prefer). A link to authorize the Deployment will be posted as a comment on the Pull Request.
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 email@example.com
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 formatted
If you are still having issues after considering all of the above, please visit http://vercel.com/help and share the most recent git SHA in question.