github: scripts: Skip validations for code blocks on commit linter

[cosmo0920]

This change does not relax commit message validation rules.
It only prevents false positives caused by fenced code blocks
commonly used to include logs, YAML configs, or command output
in Fluent Bit commit messages.

---

Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

• Example configuration file for the change
• Debug log output from testing the change

• Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

• Run local packaging test showing all targets (including any new ones) build.
• Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

• Documentation required for this feature

Backporting

• Backport to latest stable release.

---

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Summary by CodeRabbit

• Chores

  • Commit validation now ignores fenced code blocks in message bodies.
  • Multi-prefix handling improved: umbrella prefixes may cover multiple components; otherwise validation returns clearer expected-prefix errors.

• Tests

  • Added tests ensuring commit messages containing fenced code blocks pass validation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request adds support for stripping fenced code blocks from commit messages before validation. A new regex pattern and strip_fenced_code_blocks() function is introduced and applied to commit body parsing in squash detection and commit validation. Additionally, multi-prefix handling logic is refined to allow umbrella prefixes to cover multiple components when needed.

Changes

Cohort / File(s)	Summary
Fenced code block stripping & prefix validation ​.github/scripts/commit_prefix_check.py	Added FENCED_BLOCK_RE regex and strip_fenced_code_blocks() function to remove code fences from commit bodies. Applied sanitization in detect_bad_squash() and validate_commit(). Refined multi-prefix handling to allow umbrella prefixes (e.g., lib:) when multiple non-build prefixes are inferred.
Test coverage for fenced code blocks ​.github/scripts/tests/test_commit_lint.py	Added test case validating that commits with fenced code blocks (YAML examples) in the body pass validation without errors.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• workflows: add new commit linter tool #11245: Directly related; modifies commit_prefix_check.py to add strip_fenced_code_blocks function and update commit validation logic with corresponding test additions.
• github: scripts: commit_prefix_check: add config format rules on linter #11346: Modifies commit_prefix_check.py and refines validate_commit's umbrella/multi-prefix handling for configuration format rules.
• github: commit_linter: Make more flexibility for commit linter #11251: Modifies commit_prefix_check.py and adjusts commit validation logic including multi-prefix/umbrella prefix handling.

Suggested reviewers

• niedbalski
• patrick-stephens
• celalettin1286

Poem

A rabbit hops through code fences tall, 🐰
Strips them away, ignoring them all!
Squash detection runs clean and bright,
Prefixes validated just right! ✨
No blocked code shall cause dismay,
Commit linting saves the day!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: adding functionality to skip commit linter validations for code blocks in commit messages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In @.github/scripts/commit_prefix_check.py:
- Around line 238-246: The current branch allows umbrella prefixes (checked via
subj_lower in umbrella_prefixes) even when the commit touches mixed components;
modify the block inside the len(non_build_prefixes) > 1 check to only accept
umbrella prefixes when all changed file paths belong to the umbrella domain(s)
(e.g., all paths start with the umbrella directory like "lib/"); specifically,
when evaluating subj_lower against umbrella_prefixes, add a predicate that
verifies every changed path in the commit is within the umbrella directories
before returning success, otherwise treat it as a mismatch and return the
existing False with expected_str (using subject_prefix, non_build_prefixes,
umbrella_prefixes, and expected to locate and adjust the logic).

In @.github/scripts/tests/test_commit_lint.py:
- Around line 207-208: The test assigns a second return value to msg from
validate_commit(commit) but never uses it; rename msg to _ or _msg to satisfy
RUF059. Update the line "ok, msg = validate_commit(commit)" to "ok, _ =
validate_commit(commit)" or "ok, _msg = validate_commit(commit)" so the unused
variable is clearly ignored while keeping validate_commit and commit references
intact.