heygrc and Mergify

Different jobs, same pull request.

Mergify decides how and when a change merges, not what is in it. heygrc reads the change for the compliance control it touches. A change can merge cleanly through automation and still skip the review step a control depends on.

Get early access by ISMS Copilot

Mergify

Mergify automates how pull requests merge: merge queues, automatic merging, and CI rules. It is not a code reviewer.

heygrc

heygrc reviews each pull request against the compliance frameworks your company must meet (ISO 27001, SOC 2, GDPR, and more) and cites the specific control a change touches. It is built for compliance, not code quality.

Where they do not overlap

An automation rule that merges without review.

This change adds a rule that auto-merges any pull request labeled hotfix once CI is green, with no review required. It works as configured.

.mergify.yml+5 −0

pull_request_rules:+  - name: auto-merge hotfixes+    conditions: [label=hotfix, check-success=ci]+    actions:+      merge: {}

heygrcISO 27001 A.8.32

The rule does exactly what it says and speeds up hotfixes. But auto-merging with no review means changes reach the main branch with no authorization step, which is change management under ISO 27001 A.8.32. heygrc is built to read a configuration change like this against your frameworks and cite the control it touches.

Use them together

Keep Mergify. Add the compliance layer.

This is not a question of which tool wins. Mergify catches the bugs and quality problems heygrc never looks for, and heygrc catches the compliance issues a code review is not built to see. Running both means a pull request is checked for whether the code is good and for whether the change is compliant, two different kinds of risk, on the same diff.

heygrc does not replace your code review, and it does not certify you. It reviews changes against your frameworks and cites the control, so the compliance question is answered where the change is made. heygrc is in early access.

Get early access ← Where heygrc fits

Questions

heygrc and Mergify, common questions.

Is heygrc an alternative to Mergify?

Not exactly. Mergify reviews your code; heygrc reviews each change for compliance against the frameworks your company must meet (ISO 27001, SOC 2, GDPR, and more) and cites the specific control it touches. They answer different questions about the same pull request, so heygrc is designed to run alongside it, not replace it.

Can I use heygrc and Mergify together?

Yes. They look at different kinds of risk on the same diff: Mergify on the code, heygrc on the compliance control a change touches. heygrc does not replace your code review.

What does heygrc check on a pull request?

heygrc reviews each pull request against the frameworks your company selected and cites the specific control a change touches, so the compliance question is answered in code review. heygrc does not certify you and is in early access.