ci(deps): stop include:scope doubling the scope the prefixes already carry - #103
Merged
Conversation
…carry Each prefix here already ends in its scope -- chore(deps), ci(deps), build(docker) -- and include: "scope" appends another one, so the first pull request written by the now-live config merged as 'ci(deps)(deps): bump azure/login from 2.3.0 to 3.0.2'. This was invisible until now: include: "scope" arrived on 2026-08-07 in the same commit that invalidated the file, so Dependabot never applied it and kept titling from the older config. Dropping it restores exactly the prefixes each block declares, rather than restating each one bare and leaving include: to rebuild it.
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
1 participant
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.
Follow-up to #100, which made
.github/dependabot.ymltake effect again after three weeks of being rejected. With the file finally live, a second problem in the same 2026-08-07 commit became visible.Every prefix in this file already ends in its own scope —
chore(deps),ci(deps),build(docker)— andinclude: "scope"appends another one. The first PR Dependabot re-titled under the live config merged as:include: "scope"was added on 2026-08-07, the same commit that invalidated the file, so Dependabot never applied it and went on titling from the older config. The doubling has been latent ever since and only appeared once #100 landed.Removing
include: "scope"from all four blocks restores exactly the prefix each block declares:chore(deps)(deps):chore(deps):chore(deps)(deps):/chore(dev-deps)(deps-dev):chore(deps):/chore(dev-deps):ci(deps)(deps):ci(deps):build(docker)(deps):build(docker):The alternative — reducing each prefix to a bare type and letting
include:rebuild the scope — would dropdockerfrom the Docker prefix and make npm'sprefix-developmentredundant. Keeping the prefixes as authored is the smaller change and preserves what each one was chosen to say.Also created the four labels this file references that did not exist in the repo —
dotnet,frontend,ci,docker— which Dependabot had started reporting on every PR:That warning was also new, and for the same reason: the label list was never read while the config was being rejected.