| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Unresolved correctness and permission issues prevent reliable, accurate dequeue notifications.
4 open issuesAdds an internal GitHub Actions workflow to make merge-queue removals more visible through pull request comments.
Changes:
| File | Description |
|---|---|
| .github/workflows/pr-dequeued.yml | Adds the dequeue-triggered notification workflow and comment command. |
Review effort: Max
Sorry, something went wrong.
| name: PR dequeued | ||
|
|
||
| on: | ||
| pull_request: |
There was a problem hiding this comment.
Absolutely not.
Sorry, something went wrong.
|
@github-merge-queue[bot] The pull request was removed from the merge queue (CI_FAILURE). Please resolve any issues if required and enqueue the PR again. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
To make this more visible.
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