Skip to content

chore(merge): land green PRs with Mergify - #31

Merged
guillaume-flambard merged 1 commit into
mainfrom
chore/mergify-autoloop
Oct 17, 2026
Merged

guillaume-flambard merged 1 commit into
mainfrom
chore/mergify-autoloop

Conversation

@guillaume-flambard

Copy link
Copy Markdown
Collaborator

Why

Owner decision of 2026-10-17 (memolabs-dev/memo-bridge#149, #151): a green pull request from memo-labs-automation[bot] or guillaume-flambard lands without a human; only sensitive paths wait for the owner. memo-bridge runs this policy since #154; its canaries passed (memolabs-dev/memo-bridge#155 merged by Mergify, memolabs-dev/memo-bridge#156 held on deploy/). Template and procedure: docs/MERGIFY_FLEET_ADOPTION.md in memo-bridge.

Policy in this repository

Lands when, on the exact head: base main, not draft, not from a fork, trusted author, no hold-merge / needs-human-review label, no sensitive path, required check(s) green. One PR at a time.
Sensitive: .github/, .mergify.yml, CODEOWNERS, root AGENTS.md, deploy/, ansible/, infra/, stacks/, root .env*, any migrations/ directory.
Required checks: test (22), test (24). Merge method: merge, matching the merge commits on main so far.

What changes

  • .mergify.yml added. There was no merge engine: the owner merged by hand.
  • AGENTS.md and .github/pull_request_template.md: they told the retired drop-agent-bot to arm GitHub auto-merge. They now say Mergify merges and agents never run gh pr merge.

Open PRs

#30 (non-draft, by the owner) would become eligible. Per the no-retroactive rule it gets hold-merge; remove the label when you want Mergify to take it.

After merge

Positive and negative canary, as on memo-bridge.

This PR touches .mergify.yml, .github/ and AGENTS.md: the owner merges it.

Adds the Memo Labs fleet .mergify.yml (required checks test (22) and test (24), merge
commits as before) and updates AGENTS.md and the PR template, which still named the retired
drop-agent-bot and GitHub auto-merge.

Refs memolabs-dev/memo-bridge#149
@mergify

mergify Bot commented Oct 17, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 📃 Configuration Change Requirements

Mergify configuration change

  • any of:
    • check-success = @mergify/Configuration changed
    • check-success = @mergify/Configuration has been deleted

@mergify

mergify Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again.

@guillaume-flambard
guillaume-flambard merged commit d0b985f into main Oct 17, 2026
5 checks passed
@guillaume-flambard
guillaume-flambard deleted the chore/mergify-autoloop branch October 17, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant