COMPARISON

GitHub required checks enforce process. Mo enforces approved rules.

GitHub required checks make sure required validations pass before merge. Mo adds a different check: whether the pull request still follows approved pricing, permission, onboarding, and product rules.

See 10s demo Start free trial

Mo works with Slack, GitHub, and GitLab.

GitHub Required checks · Pull request #114
✓
CI / build passed
✓
Tests (138 passed) passed
✓
Review approved approved
✓
Lint passed
All required checks passed
Mo
mo-bot
Approved rule conflict detected
Approved: Only admins can export users
PR grants: export access to all roles
CONFLICT WITH APPROVED RULE

What GitHub required checks are good at

01
Build and test status

GitHub required checks are great for enforcing that CI, tests, and status checks pass before merge.

02
Review process

They help enforce branch protection, approvals, and merge requirements.

03
Standard workflow controls

They make sure the normal engineering process is followed.

What they do not tell you

A required check can pass even when the pull request breaks an approved business rule.

✓The tests may pass.
✓The build may pass.
✓The review may pass.
✗The code may still ship the wrong behavior.
That is the gap Mo fills.

Mo adds a rule-level check before merge

Rule approved

"Only admins can export users."

Pull request opened

Export access is expanded to non-admin users.

Result
GitHub required checks can still be green.
Mo flags the pull request because it breaks the approved rule.

Side-by-side

Capability GitHub required checks Mo
Enforce CI / tests before merge Yes No
Enforce approvals / branch rules Yes No
Check approved pricing rules No Yes
Check approved permission rules No Yes
Check approved onboarding rules No Yes
Flag drift from Slack-approved rules No Yes
Catch business-rule changes before merge No Yes

Why teams use Mo with GitHub required checks

GitHub required checks and Mo fit together.

GitHub required checks answer:
did the normal engineering validations pass?

Mo answers:
did this pull request break an approved rule?

That combination is much stronger than either one alone.

Example cases Mo covers

Pricing
Trial length changed without approval
Permissions
Guest users gained billing access
Onboarding
Users can start a trial before email confirmation
Compliance-sensitive logic
Restricted regions gained access to a protected feature

The easiest way to think about it

GitHub Required checks protect the merge process.
Mo Mo protects the approved product logic.

FAQ

Does Mo replace GitHub required checks?

No. Mo adds a rule-level check on top of GitHub's process-level checks.

Can Mo run as a required check?

Yes. Teams can use Mo as part of the checks that run before merge.

Why is this needed if tests already pass?

Because a pull request can pass tests and still break an approved business rule.

Used internally at Advante across 12+ projects including:

Keep GitHub required checks. Add the check they do not give you.

Use Mo to flag pull requests that break approved rules before merge.

Start free trial See 10s demo