Skip to content

merge queue: embarking main (ce0a382), #405 and #413 together#415

Closed
mergify[bot] wants to merge 4 commits intomainfrom
mergify/merge-queue/8914a67029
Closed

merge queue: embarking main (ce0a382), #405 and #413 together#415
mergify[bot] wants to merge 4 commits intomainfrom
mergify/merge-queue/8914a67029

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 5, 2026

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

Branch main (ce0a382), #405 and #413 are embarked together for merge.

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

mergify Bot and others added 4 commits May 1, 2026 06:57
The stack prev/next nav at the top of a PR page used to always link to
the bare PR URL, dropping the user back onto the Conversation tab. Now
the link forwards whatever subpath the user is currently viewing
(`/changes`, `/files`, `/commits`, …) so navigating between PRs in a
stack keeps you on the same tab.

Hash and query are intentionally not preserved — they typically point at
PR-specific content (a diff anchor, a comment) that won't apply to the
target PR.

Change-Id: Ic8087dddcb12b508e8b2837e2b4c43bf41a66d86
@mergify mergify Bot deployed to Mergify Merge Protections May 5, 2026 10:11 Active
@mergify mergify Bot closed this May 5, 2026
@mergify mergify Bot deleted the mergify/merge-queue/8914a67029 branch May 5, 2026 10:13
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