Skip to content

ci: pin Dependabot commit message prefix - #260

Merged
fuzzzerd merged 1 commit into
masterfrom
fuzzz/pin-dependabot-commit-prefix
Aug 19, 2026
Merged

ci: pin Dependabot commit message prefix#260
fuzzzerd merged 1 commit into
masterfrom
fuzzz/pin-dependabot-commit-prefix

Conversation

@fuzzzerd

Copy link
Copy Markdown
Owner

Dependabot PR titles drifted off the chore(deps): convention — #249, #253, #254, and #255 landed as bare Bump ....

.github/dependabot.yml had no commit-message block, so Dependabot inferred the prefix from recent commit history. That inference is unstable: once a few unprefixed bumps land, it stops prefixing, and the drift reinforces itself.

Each ecosystem now pins prefix: chore, prefix-development: chore, and include: scope, producing chore(deps): Bump ....

Neither the NuGet nor the github-actions ecosystem classifies development dependencies, so prefix-development is inert today — it is set so a future ecosystem that does classify them stays consistent.

Without an explicit commit-message block, Dependabot infers the prefix from recent commit history, so it dropped chore(deps) once a few unprefixed bumps landed. Setting prefix, prefix-development, and include: scope on every ecosystem keeps PR titles consistent.
@github-actions

Copy link
Copy Markdown

Test Results

✔️ Tests 2343 / 2343 - passed in 16s
✔️ Coverage 80.31% - passed with 70% threshold
📏 11693 / 13732 lines covered 🌿 3676 / 5406 branches covered
🔍 click here for more details

✏️ updated for commit 1d3dfdc

@fuzzzerd
fuzzzerd merged commit 128ee01 into master Aug 19, 2026
6 checks passed
@fuzzzerd
fuzzzerd deleted the fuzzz/pin-dependabot-commit-prefix branch August 19, 2026 22:14
fuzzzerd added a commit that referenced this pull request Aug 19, 2026
Follow-up to #260. That change pinned `prefix: chore` with `include:
"scope"`, but the recreated group PRs (#261, #262) came back as `chore:
Bump the nlog group with 2 updates` — the `(deps)` scope was never
added.

`include: "scope"` derives the scope from dependency-type resolution,
which produces nothing for these ecosystems. Spelling the scope directly
into `prefix` and `prefix-development` makes the title deterministic:

```
chore(deps): Bump the nlog group with 2 updates
```

`include` is dropped, since keeping it alongside a prefix that already
carries a scope risks emitting it twice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant