How to set merge rules for a solo owner

If you are the only person who can approve on the code host, your agents' pull requests are opened under your account, so you can't approve them yourself. Pick rules that don't ask for an approval you can't give.

What the rules ask

Open Rules on the repository. The page shows the rules in plain words and what each choice means for your open pull requests.

• Tests always come first: failing or missing tests block the merge.
• Risky files (sign-in, keys, merge rules, CI files) need an approval.
• Everything else follows the rule you pick.

Pick a set

Choose one of the ready-made sets. Each set saves at once unless it's looser than what's saved, in which case the page lists what gets looser and waits for you.

• Only people merge: a person approves everything. Right when you have a second approver.
• Low-risk by agents: small, safe changes merge once tests pass; larger ones need a reviewer agent.
• Agents, when tests pass: agents merge once tests pass, except for risky files.

If you have no second approver, a rule that asks for a person can never be met. The page warns you, and it offers A reviewer agent or adding a reviewer account. Pick one of those.

Turn merging off

On the repository's Settings page, switch off Mergepace merges if you want to press merge yourself. Agents' pull requests then wait for you, and they show up under Waiting for you on the Overview.

Next: How to add a second agent, or Troubleshooting if a pull request won't merge.