Does heyGRC block merges?

Does heyGRC block my pull requests from merging?

Short answer: no, not on its own. heyGRC posts its review as a comment. It never submits a "Request changes" review, and its status check is never a failure on findings (only neutral or success). So by default heyGRC cannot stop a merge.

But one GitHub setting can turn heyGRC's comments into a merge gate. If your repository has the branch rule "Require conversation resolution before merging" enabled, then GitHub requires every unresolved review conversation on the PR, including a bot's, to be marked resolved before you can merge. heyGRC leaves line-anchored inline comments on the exact lines of a finding, and those inline comments are resolvable conversation threads. So in a repo with that rule on, you will need to click "Resolve conversation" on each heyGRC finding before GitHub lets you merge.

A few clarifying points:

• This is your repository's branch rule doing the gating, not heyGRC forcing a block. heyGRC's own signals (the review verdict and the status check) stay non-blocking either way.
• Only heyGRC's inline comments (attached to a changed line) create resolvable threads. heyGRC's top-level review summary is a normal comment and never gates a merge.
• For a compliance workflow this is often desirable: resolving each finding is a lightweight, recorded acknowledgment that the team saw and addressed (or accepted) the control impact before merging.

What to do if you do not want heyGRC findings to gate merges

• Keep resolving them (recommended): address or acknowledge each finding, then click "Resolve conversation." This preserves the acknowledgment trail and keeps merges flowing.
• Or relax the branch rule: turn off "Require conversation resolution before merging" for that branch. Find it under Settings, then Branches or Rules, in the branch protection rule / ruleset. With it off, no reviewer's comments (heyGRC's or a human's) will gate a merge.

Where this setting lives

Repository Settings, then Branches (classic branch protection) or Rules (rulesets), then your protected-branch rule, then "Require conversation resolution before merging."

See also: Use with your code reviewer for how heyGRC coexists with code-review bots, and Set up with your agent for review modes (auto, auto_once, mention_only).