Skip to content

merge queue: embarking main (b7f3c96) and #1407 together#1417

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/12c88e2398
Closed

merge queue: embarking main (b7f3c96) and #1407 together#1417
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/12c88e2398

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 13, 2026

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

Branch main (b7f3c96) and #1407 are embarked together for merge.

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

jd and others added 3 commits May 13, 2026 10:25
Pins the contract for ``mergify ci queue-info`` so the upcoming
Rust port can be validated against the same test that exercises
the Python implementation. Lands first; the port commit on top
re-runs this test against Rust — same contract, both ends.

The test doesn't need ``live_token`` (the command is locally
evaluated). The conftest fixture scrubs every event env var and
runs in a tmp dir, so the detector always reports "no MQ
context". The assertion checks for exit code 7 (``INVALID_STATE``)
and an MQ-context message in stdout or stderr.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: Idff72acfc1f35f7f64051a4f62a3fe625d2b802f
The Rust binary now serves ``mergify ci queue-info`` natively.
The Python implementation (``mergify_cli/ci/cli.py:queue_info``)
and its tests are removed in the same PR — port-and-delete keeps
a single live copy.

The previous commit landed a live-smoke test pinning the
``INVALID_STATE`` exit code outside an MQ context. That same
test now exercises the Rust path.

``ci queue-info`` prints the merge-queue batch metadata embedded
in the current draft PR as pretty JSON. Outside an MQ context
(no event payload, no PR body fenced block) it exits
``INVALID_STATE`` (exit 7).

When ``$GITHUB_OUTPUT`` is set (GitHub Actions runner), the
command also appends the metadata as ``queue_metadata`` under a
random ``ghadelimiter_<uuid>`` heredoc, matching the pattern
GitHub Actions expects for multi-line workflow outputs.

The implementation reuses the shared ``queue_metadata`` and
``github_event`` modules introduced by the previous (git-refs)
port commit.

Adds the ``uuid`` dep (v4 random UUIDs for the ghadelimiter) to
the ``mergify-ci`` crate.

3 new queue-info tests in the ``mergify-ci`` crate. The Python
queue-info tests in ``test_cli.py``, ``test_cli_exit_codes.py``,
and ``test_exit_code_contract.py`` are removed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: If0cdc5a06685387f6a9379b237eb5d184b071dc4
@mergify mergify Bot deployed to Mergify Merge Protections May 13, 2026 13:36 Active
@mergify mergify Bot temporarily deployed to func-tests-live May 13, 2026 13:36 Inactive
@mergify mergify Bot closed this May 13, 2026
@mergify mergify Bot deleted the mergify/merge-queue/12c88e2398 branch May 13, 2026 13:51
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