Git Configuration
The following configuration options can be used through a file like the Project Configuration.
Type: of key branch identifier and value , or .
Default:
Specify branches that should not trigger a deployment upon commits. By default, any unspecified branch is set to .
Use minimatch syntax to define behavior for multiple branches.
The example below prevents automated deployments for any branch that starts with .
If a branch matches multiple rules and at least one rule is , a deployment will occur.
A branch named will create a deployment.
To turn off automatic deployments for all branches, set the property value to .
Type: .
When set to , Vercel for GitHub will create preview deployments upon merge.
Follow the deploying a staged production build workflow instead of this setting.
Type: .
When set to false, Vercel for GitHub will always build pushes in sequence without cancelling a build for the most recent commit.
The property has been deprecated in favor of the new settings in the dashboard, which allow for more fine-grained control over which comments appear on your connected Git repositories. These settings can be found in the Git section of your project's settings.
Type: .
When set to , Vercel for GitHub will stop commenting on pull requests and commits.
The property has been deprecated in favor of git.deploymentEnabled, which allows you to disable auto-deployments for your project.
Type: .
When set to , Vercel for GitHub will not deploy the given project regardless of the GitHub app being installed.
Was this helpful?