Skip to content

merge queue: queuing main (b2529cf), #1615 and #1616 together#1623

Closed
mergify[bot] wants to merge 5 commits into
mainfrom
mergify/merge-queue/73ea1a8a5d
Closed

merge queue: queuing main (b2529cf), #1615 and #1616 together#1623
mergify[bot] wants to merge 5 commits into
mainfrom
mergify/merge-queue/73ea1a8a5d

Conversation

@mergify

@mergify mergify Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

⏳ The pull request #1616 is queued for merge and currently being checked. ⏳

Branch main (b2529cf), #1615 and #1616 are queued together for merge.

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

JulianMaurin and others added 5 commits June 16, 2026 20:23
`stack push` rendered only `log_lines` and discarded the planned/upserted data, so the "Stacked pull request plan" preview and per-PR `[created] … <url>` summary were missing. Port `get_log_from_local_change` / `get_log_from_orphan_change` as plain-text formatters and emit the plan, created, and orphan-deleted lines into `log_lines` in flow order (dry-run included).

`push_branches` ran `git push` with inherited stdio, leaking git's `remote:` ruleset-bypass and branch-creation narration. Capture it and surface stderr only on failure, matching `run_git_silent`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: Ic1a22ea2f054a6a38df6ff5aff569ae9573fce22
The dry-run rebase narration and the revision-history change-type fetch warning carried literal `[orange]…[/]` Rich tags. Python rendered them through a markup-aware console (tags stripped off a TTY, styled on one); the Rust CLI prints log lines verbatim with no markup renderer, so users saw the literal bracket tags. Drop the tags so the lines read as plain text, consistent with the rest of the CLI's output.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I3b8c1ed7b55f6d806f871ad86878fc375d9eade1
A failed `git rebase -i` in spawn_rebase returned a generic "exited <status>" error mapped to exit 1. Every rebase-driving command (drop, squash, fixup, reorder, reword, move, edit, sync) routes through this helper, so all of them lost the conflict recovery instructions and the dedicated Conflict exit code (4) that automation keys on. Return CliError::Conflict with the resolve/continue/abort guidance, matching the Python run_scripted_rebase contract.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I5dff7d8117910398fcd0abc2cc39027744ff1cf7
@mergify mergify Bot deployed to Mergify Merge Protections June 17, 2026 07:32 Active
@mergify mergify Bot temporarily deployed to func-tests-live June 17, 2026 07:32 Inactive
@mergify mergify Bot closed this Jun 17, 2026
@mergify mergify Bot deleted the mergify/merge-queue/73ea1a8a5d branch June 17, 2026 07:38
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