test(ci): add live smoke test for ci queue-info#1406
Merged
mergify[bot] merged 1 commit intoMay 13, 2026
Merged
Conversation
Member
Author
|
This pull request is part of a Mergify stack:
|
This was referenced May 11, 2026
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 🤖 Continuous IntegrationWonderful, this rule succeeded.
🟢 👀 Review RequirementsWonderful, this rule succeeded.
🟢 Enforce conventional commitWonderful, this rule succeeded.Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 ReviewsWonderful, this rule succeeded.
🟢 📕 PR descriptionWonderful, this rule succeeded.
|
This was referenced May 11, 2026
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-ci-queue-info--dff72acf
branch
from
2df5670 to
9455954
Compare
Member
Author
Revision history
|
jd
force-pushed
the
devs/jd/worktree-rust-port/port-ci-git-refs-native-rust--9a936b47
branch
from
0d7c20c to
d0a28d3
Compare
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-ci-queue-info--dff72acf
branch
from
9455954 to
028653c
Compare
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-ci-queue-info--dff72acf
branch
from
028653c to
754a755
Compare
There was a problem hiding this comment.
Pull request overview
Adds a live smoke-test contract for mergify ci queue-info to ensure consistent behavior (especially exit code + user-facing messaging) before and after the upcoming Python → Rust port.
Changes:
- Add a functional smoke test that runs
mergify ci queue-infowith no merge-queue context. - Assert the command exits with
INVALID_STATE(7). - Assert the output includes a merge-queue context message (stdout or stderr).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-ci-queue-info--dff72acf
branch
from
754a755 to
810b36f
Compare
Base automatically changed from
devs/jd/worktree-rust-port/port-ci-git-refs-native-rust--9a936b47
to
main
May 12, 2026 14:20
Contributor
|
@jd this pull request is now in conflict 😩 |
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
jd
force-pushed
the
devs/jd/worktree-rust-port/add-live-smoke-test-ci-queue-info--dff72acf
branch
from
810b36f to
7912fee
Compare
JulianMaurin
approved these changes
May 13, 2026
sileht
approved these changes
May 13, 2026
Contributor
Merge Queue Status
This pull request spent 16 seconds in the queue, including 2 seconds running CI. Required conditions to merge
|
mergify
Bot
deleted the
devs/jd/worktree-rust-port/add-live-smoke-test-ci-queue-info--dff72acf
branch
38 tasks
mergify Bot
pushed a commit
that referenced
this pull request
May 13, 2026
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> Depends-On: #1406
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins the contract for
mergify ci queue-infoso the upcomingRust 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 locallyevaluated). 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