[clintval]

The ci parser in the git-cliff config was ^ci*, which matches any commit starting with c, so chore(release) bumps and dependabot's chore(deps) updates landed under "Continuous Integration" before the rules that skip them. 4.2.1 listed its bump and three dependabot updates there.

The parser now matches only ci: and ci(scope): commits. Running git-cliff over 4.2.0..4.2.1 with the new config lists only #86 under "Build", with the bump and the dependabot updates skipped as the config intends. The same fix landed in clintval/captainslog#7.

Summary by CodeRabbit

• Chores
  • Continuous Integration changelog entries now require a ci: or ci(scope): subject format.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The git-cliff Continuous Integration parser now matches commit subjects that start with ci: or ci(scope):. It no longer uses the broader ^ci* pattern.

Changes: CI Commit Subject Matching

Layer / File(s)	Summary
Update CI subject pattern pyproject.toml	The Continuous Integration parser pattern now requires ci: or ci(scope): at the start of the commit subject.

Priority: Not assessed

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: Minimal · up to c5e55

The CI parser change is ready to merge.

Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}