Skip to content

merge queue: checking #1798 on main (5952690) - #1812

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/9be20d95f8
Closed

merge queue: checking #1798 on main (5952690)#1812
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/9be20d95f8

Conversation

@mergify

@mergify mergify Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#1798 is queued for merge on branch main (5952690).

This pull request has been created by Mergify to check the mergeability of #1798.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 5952690f70ad0f2b1702a866c41e59e1b1a617e2
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1798
    scopes: []
scopes: []
...

jd and others added 2 commits September 4, 2026 16:37
MRGFY-9001 cut the `ci` application key to what a CI job actually
needs, and `GET /ci/{owner}/repositories/{repo}/search/tests` lost
`ci_application_key` along with it. `tests_show_no_match` still
passed the CI-scoped token, so every live run since has failed with
a 403 on that one test — on pull requests that touch nothing near
it.

Reading test health is a developer inspecting a repository, not
something a CI job does, so the 403 is the intended answer and the
test was asserting an obsolete contract. It moves to the admin
token, under the admin banner with the queue and freeze tests that
were separated for the same reason.

The narrowing also took the two quarantine mutations the CLI makes
(`tests quarantines add` and `remove`); no live test covers those,
so they broke silently. Three doc surfaces promised any token
worked, and AGENTS.md makes README and `--help` the owners of the
token contract, so all three now say which key each command needs:

- `skills/mergify-ci/SKILL.md` grows one `## Authentication`
  section glossing the two key classes, replacing the per-command
  repetition the sibling merge-protections skill already avoids.
  It also states the rule for the commands that keep working, so
  the silence on `quarantines list`/`get` is readable rather than
  looking like an oversight.
- README documents the split at group altitude, next to the
  existing token resolution order.
- `--help` for the three affected commands says it inline. Those
  doc comments feed `cli_schema.rs`, which the docs site renders,
  so the golden snapshot moves with them.

While in that section: the `tests show` exit-code table claimed `1`
= flaky and `6` = broken, but `tests_show::run` returns
`ExitCode::Success` on every rendered path — pinned by
`unhealthy_tests_still_exit_success`. A CI gate written from that
table never fired, and it read this commit's own 403 (exit 6, a
`CliError`) as "a broken test". Corrected to what the command does.

Nothing in `Mergifyio/mergify-ci-integrations` is affected: its
whole API surface is `traces`, `quarantines` (list),
`flaky-detection-context` and `test-selection`, all of which the
narrowing kept.

Verified on CI: run 33880789655 reports `tests_show_no_match ... ok`
with 12/12 green, so the admin key does carry CI-Insights read
scope. `search/tests` is the only route the suite covers —
`tests/{test_id}` is narrowed the same way but the no-match query
returns before the details fetch, which the helper's doc now says.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JBz3hxMUDCuWftT6qAHtnn

Change-Id: I4e4c3e308adb7dbd68052ef9b03c2e42381dd8ce
@mergify
mergify Bot deployed to Mergify Merge Protections September 7, 2026 11:12 Active
@mergify
mergify Bot deployed to func-tests-live September 7, 2026 11:12 Active
@mergify mergify Bot closed this Sep 7, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/9be20d95f8 branch September 7, 2026 11:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant