Ping the user who enqueued a PR when it's removed from the merge queue - #4265
Merged
henrymercer merged 2 commits intoOct 27, 2026
Merged
henrymercer merged 2 commits into
henrymercer merged 2 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
A failed recipient lookup stops the workflow before it posts the dequeue notification.
1 open issue What changed in this PRUpdates the repository’s merge-queue notification workflow to notify the person who enqueued a PR rather than its author, avoiding mentions of bot authors.
Changes:
- Queries the PR timeline for the latest merge-queue enqueuer.
- Uses that user’s login in the dequeue notification.
| File | Description |
|---|---|
| .github/workflows/pr-dequeued.yml | Looks up and mentions the latest enqueuer in dequeue comments. |
Review effort: Max
Sorry, something went wrong.
Comment thread
.github/workflows/pr-dequeued.yml
Resolved
henrymercer
marked this pull request as ready for review
October 23, 2026 12:45
mbg
approved these changes
Oct 27, 2026
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.
Follow-up to #4263. When a PR is removed from the merge queue, the comment now mentions the user who most recently added it to the queue rather than the PR author. This avoids pinging bots on PRs authored by Dependabot or Actions, which maintainers enqueue.
The dequeued event payload doesn't identify the enqueuer, so the workflow looks them up in the most recent AddedToMergeQueueEvent on the PR's timeline. If auto-merge added the PR to the queue, this event is attributed to the user who enabled auto-merge.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist