Skip to content

merge queue: embarking main (d641cb3), #1362 and #1351 together#1370

Closed
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/3dadce3e11
Closed

merge queue: embarking main (d641cb3), #1362 and #1351 together#1370
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/3dadce3e11

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 6, 2026

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

Branch main (d641cb3), #1362 and #1351 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #1351.
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: fad87408923c62383e26fc3d3128a3bde792c73c
previous_failed_batches: []
pull_requests:
  - number: 1351
    scopes: []
scopes: []
...

sileht and others added 4 commits May 5, 2026 19:25
Three smoke tests under func-tests/ that drive the real `mergify`
binary against the real Mergify API, gated on
LIVE_TEST_MERGIFY_TOKEN:

- `ci scopes-send` — POST /v1/repos/{owner}/{repo}/pulls/{n}/scopes
- `ci junit-process` — OTLP traces upload + quarantine check
- `config simulate` — POST /v1/repos/{owner}/{repo}/pulls/{n}/simulator

Each fires when the real API's URL, auth, or wire format diverges
from what the CLI expects. Asserts only "endpoint exists, accepts
our payload, returns 2xx" — never response content, since the
test tenant's state is not under test control.

Driven by `.github/workflows/func-tests-live.yaml` on a nightly
cron + manual dispatch against
mergify-clients-testing/mergify-cli-repo PR #1. Runs in a
dedicated `func-tests-live` GitHub Environment so the
LIVE_TEST_MERGIFY_TOKEN secret can be rotated and audited
independently. NOT wired into the PR ci-gate — an upstream blip
cannot block PRs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: I1ee94f6c9e1d6ac7d4ad22fe07b98860ecec12e9
Status was implicit: every entry was `shimmed`, and ports flip status
by deleting the entry (because the Python copy is removed in the same
PR). Tracking that in TOML adds a step that does no work — the truth
is "command exists in click → shimmed; doesn't → ported or never
existed."

Drop the inventory file plus its guard test; document the
port-and-delete rule in AGENTS.md so the structural anti-drift
contract survives losing the file's header comment.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: I77522cb91d59b41815a98869953bff331ede3941
@mergify mergify Bot deployed to Mergify Merge Protections May 6, 2026 08:35 Active
@mergify mergify Bot temporarily deployed to func-tests-live May 6, 2026 08:35 Inactive
@mergify mergify Bot closed this May 6, 2026
@mergify mergify Bot deleted the mergify/merge-queue/3dadce3e11 branch May 6, 2026 08:49
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.

2 participants