Skip to content

docs(contributing): make AI-review-comment handling an explicit convention #728

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blove merged 1 commit into from
Jun 23, 2026
Merged

docs(contributing): make AI-review-comment handling an explicit convention #728

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,6 +47,12 @@ not a required check and never blocks a merge. A second workflow
Scorecard's Code-Review check reads from the reviews API. The maintainer still
merges every PR.

Because the review is advisory, **handling its comments is a convention, not a
gate**: before arming auto-merge, the author reads each AI comment and either
addresses it in a follow-up commit or replies on the thread with the reason for
deferring/declining. Don't merge past unread review comments — the check going
green (or red) says nothing about whether the comments were considered.

This credits Code-Review via automation rather than peer review, because the
project is currently single-maintainer. OSSF documentation suggests
automated/AI reviews may not be intended to count toward this check; the current
Expand Down
Loading