Skip to content

NAS-142294 / 27.0.0-BETA.1 / fix: do not grade stale comments as MEDIUM - #12

Merged
william-gr merged 1 commit into
iXsystems:masterfrom
agent-stewie:fix/comments-are-not-medium
Aug 20, 2026
Merged

NAS-142294 / 27.0.0-BETA.1 / fix: do not grade stale comments as MEDIUM#12
william-gr merged 1 commit into
iXsystems:masterfrom
agent-stewie:fix/comments-are-not-medium

Conversation

@agent-stewie

@agent-stewie agent-stewie commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Why

Callers fail Automatic PR review on any finding at MEDIUM or above. Item 2 of this rubric currently maps a comment or doc describing behaviour the code does not have to MEDIUM. Combined with “a finding that is still true still goes in the structured output,” every half-wrong code comment holds the merge.

That showed up on iXsystems/truenas-file-manager as a queue of PRs gated on stale comments, CI annotation wording, and pre-existing product behaviour a test PR merely discovered. The reviewer was following this file.

The gate threshold itself (MEDIUM+) does not change. LOW comments can still be reported.

What changed

  • Item 2 is now an executable untrue assertion: a type, a public API/CLI/protocol/test guarantee, or a test that cannot fail / certifies the wrong walk.
  • Comments, commit messages, internal docs, and CI annotation text that disagree with the code beside them are LOW.
  • Item 3 no longer covers “a future editor might be misled by a comment” or a CI step that still fails the job with a worse error message.
  • Pre-existing product behaviour a test/coverage PR discovered is not a finding on that PR.
  • The worked MEDIUM example is a test that certifies the wrong walk, not RELEASING.md.
  • review/schema.json severity description matches.

Public/user-facing contracts (API, CLI, protocol, published release process) still count as item 2.

Live on merge

Callers pin this workflow at @master, so this is live in every consumer on the next review run. That is the point.

Co-authored-by: William Grzybowski william@grzy.org

Callers fail the review check at MEDIUM and above. A comment or internal
doc that disagrees with the code beside it is not an executable hole, so
it is LOW. Public API/CLI/protocol/test guarantees still gate.

The worked MEDIUM example is now a test that certifies the wrong walk,
not a sentence in RELEASING.md.

Co-authored-by: William Grzybowski <william@grzy.org>
@agent-stewie
agent-stewie force-pushed the fix/comments-are-not-medium branch from 2d39bbc to 6efdf52 Compare August 20, 2026 13:32
@bugclerk bugclerk changed the title fix: do not grade stale comments as MEDIUM NAS-142294 / 27.0.0-BETA.1 / fix: do not grade stale comments as MEDIUM Aug 20, 2026
@bugclerk

Copy link
Copy Markdown
Contributor

@william-gr
william-gr merged commit 16cf688 into iXsystems:master Aug 20, 2026
6 of 8 checks passed
@bugclerk

Copy link
Copy Markdown
Contributor

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.

@iXsystems iXsystems locked as resolved and limited conversation to collaborators Aug 20, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants