Skip to content

chore: add Mergify merge-queue config [refs OSWE-238] - #3

Open
ericlitman wants to merge 1 commit into
mainfrom
chore/oswe-238-mergify-config
Open

chore: add Mergify merge-queue config [refs OSWE-238]#3
ericlitman wants to merge 1 commit into
mainfrom
chore/oswe-238-mergify-config

Conversation

@ericlitman

Copy link
Copy Markdown
Owner

Closes the last piece of OSWE-238.

Why

tonal-api is enrolled in enabled_review_repos for Open SWE review, but had none of the merge machinery the other seven enrolled repos have: no .mergify.yml, no rulesets, and allow_auto_merge disabled. The result is the silent failure OSWE-232 describes — a fully green PR sits unqueued forever, with no error anywhere.

What changed elsewhere

Already applied outside this PR:

  • allow_auto_merge enabled on this repo (and on healthspanners-ui, labctl, threadbear-web, which had the same gap).
  • A Mergify automatic merge queue ruleset created, matching the definition on the other enrolled repos: deletion, non_fast_forward, pull_request (0 required approvals), and required_status_checks requiring Mergify Merge Protections, scoped to ~DEFAULT_BRANCH.

That ruleset is currently disabled, deliberately: it requires the Mergify Merge Protections check that only the config in this PR produces, so activating it first would have blocked every merge on this repo. It gets switched to active once this lands.

This PR

Adds .mergify.yml, byte-identical to the copy in open-swe and threadbear (verified with diff).

🤖 Generated with Claude Code

tonal-api is enrolled for Open SWE review but had no merge machinery:
no .mergify.yml, no rulesets, and allow_auto_merge disabled. A fully
green PR therefore sat unqueued with no error -- the silent failure
mode OSWE-232 describes.

allow_auto_merge is now enabled and a "Mergify automatic merge queue"
ruleset matching the other seven enrolled repos has been created. This
adds the last piece: the fleet-standard Mergify config, byte-identical
to the copy in open-swe and threadbear.

The ruleset is parked as disabled until this lands, because it requires
the "Mergify Merge Protections" check that only this config produces.
It is switched to active once this merges.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mergify

mergify Bot commented Aug 3, 2026

Copy link
Copy Markdown

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 📃 Configuration Change Requirements

Mergify configuration change

  • check-success = Configuration changed

@mergify

mergify Bot commented Aug 3, 2026

Copy link
Copy Markdown

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

  • Queue this pull request

@ericlitman

Copy link
Copy Markdown
Owner Author

@open-swe review

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