Skip to content

merge queue: queuing main (13235d0) and #1619 together#1638

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/22c81f179e
Closed

merge queue: queuing main (13235d0) and #1619 together#1638
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/22c81f179e

Conversation

@mergify

@mergify mergify Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

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

Branch main (13235d0) and #1619 are queued together for merge.

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

JulianMaurin and others added 3 commits June 18, 2026 09:26
Ambiguous <COMMIT> resolution lost the "ambiguous" wording, the match count, each candidate's Change-Id, and used a 7-char SHA instead of 12. A no-match note target returned InvalidState (exit 7) instead of StackNotFound (3), and `stack open` on an empty stack exited 0 instead of 3, breaking $?-based detection. Add a shared match_commit helper (one copy of the Python reorder.py wording) used by drop/squash/fixup/edit/move/reword/reorder/note, and fix the two exit codes.

Also restore the remediation guidance Python printed: the `targets itself` error (sync/push/list) regains the remote URL and both `git branch` fix commands, and the trunk-not-resolvable error regains the concrete `--set-upstream-to` hint.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I527938955f9a8b683f5c172d330a9faaea4517d5
HTTP error rendering dumped the raw response body — so a Mergify API `{"detail": "..."}` envelope reached the user verbatim — and never showed which URL failed. Extract the JSON `detail` field when present (falling back to the raw body), and append a trailing `url:` line on HTTP errors plus the contacted URL on network/timeout errors, matching the Python check_for_status output.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I76d98c2d9a91d6ba5ad1747c91c56d4e1ade869f
@mergify mergify Bot deployed to Mergify Merge Protections June 18, 2026 08:29 Active
@mergify mergify Bot temporarily deployed to func-tests-live June 18, 2026 08:30 Inactive
@mergify mergify Bot closed this Jun 18, 2026
@mergify mergify Bot deleted the mergify/merge-queue/22c81f179e branch June 18, 2026 08:39
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