Repository navigation
Exclude Notify from required checks - #4311
Open
henrymercer wants to merge 1 commit into
Open
henrymercer wants to merge 1 commit into
henrymercer wants to merge 1 commit into
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are identified, and the change addresses the merge-queue-only Notify check by excluding it from required checks and documenting when it runs.
No open issues 🎉
What changed in this PR
This pull request excludes the merge-queue-only Notify check from required status checks so it cannot block pull requests that did not trigger it.
Changes:
- Adds
Notifyto the exact-match exclusions. - Documents that the check runs only when a pull request is removed from the merge queue.
This pull request is ready to be approved.
| File | Description |
|---|---|
pr-checks/excluded.yml |
Excludes the merge-queue-only Notify check from required checks. |
Review effort: Lite (auto)
henrymercer
marked this pull request as ready for review
November 9, 2026 11:37
This branch has not been deployed
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.
Exclude
Notifyfrom the checks thatpr-checks/sync-checks.tsmakes required. This check comes from thePR dequeuedworkflow and only runs when a PR is removed from the merge queue, so requiring it would block PRs from merging.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?
pr-checks/sync-checks.ts --ref e70c0414bf2f50ae4617cac7ffe7db16cd2bf06b, the head of a PR that had been removed from the merge queue, proposed addingNotifytomain,releases/v3andreleases/v4. With this change, the dry run excludes it and proposes no changes.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