Git settings

Once you have connected a Git repository, select the Git menu item from your project settings page to edit your project’s Git settings. These settings include:

• Specifying the production branch name
• Managing Git Large File Storage (LFS)
• Creating Deploy Hooks
• Ignoring the build step when a commit is pushed to the Git repository

To disconnect your Git repository from your Vercel project:

1. Choose a project from the dashboard
2. Select the Settings tab and then select the Git menu item
3. Under Connected Git Repository, select the Disconnect button.

If you have LFS objects in your repository, you can enable or disable support for them from the project settings. When support is enabled, Vercel will pull the LFS objects that are used in your repository.

Vercel supports deploy hooks, which are unique URLs that accept HTTP POST requests and trigger deployments. Check out our Deploy Hooks documentation to learn more.

By default, Vercel creates a new deployment and build (unless the Build Step is skipped) for every commit pushed to your connected Git repository.

Each commit in Git is assigned a unique hash value commonly referred to as SHA. If the SHA of the commit was already deployed in the past, no new Deployment is created. In that case, the last Deployment matching that SHA is returned instead.

To ignore the build step:

1. Choose a project from the dashboard
2. Select the Settings tab and then select the Git menu item
3. In the Ignored Build Step section, select the behavior you would like. This behavior provides a command that outputs a code, which tells Vercel whether to issue a new build or not. The command is executed within the Root Directory and can access all System Environment Variables:
   • Automatic: Each commit will issue a new build
   • Only build production: When the VERCEL_ENV is production, a new build will be issued
   • Only build preview: When the VERCEL_ENV is preview, a new build will be issued
   • Only build if there are changes: A new build will be issued only when the Git diff contains changes
   • Only build if there are changes in a folder: A new build will be issued only when the Git diff contains changes in a folder that you specify
   • Only build Turborepo app if there are changes: automatically detect if your project or one of its dependencies has changed and needs to be built and deployed. See the turbo-ignore docs to learn more.
   • Don't build anything: A new build will never be issued
   • Run my Bash script: Run a Bash script from a location that you specify
   • Run my Node script: Run a Node script from a location that you specify
   • Custom: You can enter any other command here, for example, only building an Nx app (npx nx-ignore <project-name>)
4. When your deployment enters the BUILDING state, the command you've entered in the Ignored Build Step section will be run. The command will always exit with either code 1 or 0:
   • If the command exits with code 1, the build continues as normal
   • If the command exits with code 0, the build is immediately aborted, and the deployment state is set to CANCELED

To learn about more advanced usage see the "How do I use the Ignored Build Step field on Vercel?" guide.

If you have set an ignore build step command or script, you can also skip the build step when redeploying your app:

1. From the Vercel dashboard, select your project
2. Select the Deployments tab and find your deployment
3. Click the ellipses (...) and from the context menu, select Redeploy
4. Uncheck the Use project's Ignore Build Step checkbox