chore: disable Vercel previews for Dependabot branches - #180
Merged
Merged
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prevents Dependabot branches from creating Vercel Preview Deployments via
git.deploymentEnabledinvercel.json.Why
dependabot/**and notdependabot/*: Vercel matches branch names with minimatch, where*never crosses/. Real Dependabot branches are nested — e.g.dependabot/npm_and_yarn/functions/eslint-10.11.0— so a single-stardependabot/*pattern matches none of them. The**glob is required for the exclusion to actually take effect.A Preview Deployment triggers downstream integrations — for projects with the Vercel↔Neon integration, each preview provisions an isolated database branch. Blocking the deployment before it is created (rather than skipping the build with an Ignored Build Step, which still creates the deployment) avoids that infrastructure entirely.
Behavior
main/masterfeat/*,fix/*, ordinary PR branchesdependabot/**Validation
vercel.jsonparses as valid JSON; all existing keys (crons, rewrites, functions, buildCommand) preservedgit.deploymentEnabled["dependabot/**"] === false; no overlappingtruerule existsdependabot/npm_and_yarn/…, 3–4 segments deep)Generated with Devin
Summary by Sourcery
Enhancements: