[mbg]

To make this more visible.

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Which use cases does this change impact?

Environments:

• Testing/None - This change does not impact any CodeQL workflows in production.

How did/will you validate this change?

• None - I am not validating these changes.

If something goes wrong after this change is released, what are the mitigation and rollback strategies?

• Development/testing only - This change cannot cause any failures in production.

How will you know if something goes wrong after this change is released?

• Other - Please provide details.

Are there any special considerations for merging or releasing this change?

• No special considerations - This change can be merged at any time.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

[Copilot]

🟡 Changes recommended

Unresolved correctness and permission issues prevent reliable, accurate dequeue notifications.

4 open issues

• Use pull_request_target for fork PR comments · New
• Skip dequeue notifications for merged pull requests · New
• Use sender.login for webhook mention · New
• Escape backticks to preserve the dequeue reason · New

What changed in this PR

Adds an internal GitHub Actions workflow to make merge-queue removals more visible through pull request comments.

Changes:

• Runs a notification job when a pull request is dequeued.
• Uses GitHub CLI to post removal details and guidance to resolve issues and re-enqueue.

File	Description
.github/​workflows/​pr-dequeued.yml	Adds the dequeue-triggered notification workflow and comment command.

_{Review effort: Max}

[mbg]

Absolutely not.