Product / Merge gate
Marlow reviews and tests its own diff before anyone looks. Then each project's merge policy decides: wait for CI, wait for an owner's approval, merge on its own tests and review, or open the pull request and stop.
- Four policies, set per project
- Self-review and tests before the pull request opens; then the policy you chose for that repository.
- A second vendor reviews the diff
- The model that reviews a change always comes from a different vendor than the model that wrote it.
- Sensitive paths need a person
- Paths you name can require a person's approval, whatever the policy.
A real run
One ticket, start to merge, with every step and every cost on the record.
cod3nest/marlow-demo · pull request 1 · merged
Start on Free
Assign it one boring ticket.
Connect a repository and hand Marlow something you have been putting off. Set the gate to “open a pull request and stop” — the worst case is a branch you close.
No card required · nothing to cancel · read the FAQ