Skip to content

merge queue: embarking main (d28e7d3) and #1225 together#1270

Closed
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/faa38e1635
Closed

merge queue: embarking main (d28e7d3) and #1225 together#1270
mergify[bot] wants to merge 2 commits intomainfrom
mergify/merge-queue/faa38e1635

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 20, 2026

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

Branch main (d28e7d3) and #1225 are embarked together for merge.

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

sileht and others added 2 commits April 20, 2026 12:46
Previously `maybe_write_to_github_outputs` emitted the literal string
`base=None` when base was None (e.g. `workflow_dispatch` events), which
leaks Python's `None` representation into workflow output. Coalesce to
an empty string so GitHub Actions steps see `base=` instead — consistent
with the new `--format=shell` behavior.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Change-Id: I25fe7c86a7c7d2aa823ef2e0fd5e71946892c7d2
@mergify mergify Bot deployed to Mergify Merge Protections April 20, 2026 15:14 Active
@mergify mergify Bot closed this Apr 20, 2026
@mergify mergify Bot deleted the mergify/merge-queue/faa38e1635 branch April 20, 2026 15:19
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