Repository navigation
Remove the Core priority support workflow and issue template - #49041
Merged
Merged
Conversation
Janpot
marked this pull request as ready for review
August 26, 2026 08:19
Janpot
added
the
scope: code-infra
Janpot
changed the title
Janpot
enabled auto-merge (squash)
August 26, 2026 08:19
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
Janpot
changed the title
Janpot
changed the title
michelengelen
approved these changes
Aug 26, 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
2 participants
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.
There is no priority support in Core, so neither of these belongs here. Both were added together in #37671 and copied from mui-x.
.github/workflows/priority-support-validation-prompt.ymlhas never worked. The link it posts hardcodesrepo=mui-x, so it sent people to validate an unrelated mui-x issue that happened to share their issue number. In the two-plus years since it was added, one issue has ever carriedsupport: unknown(#37896, July 2023, closed) and none has ever reachedsupport: priority..github/ISSUE_TEMPLATE/5.priority-support.ymlis what applied that label. Removing the workflow on its own would have left the template labelling issuessupport: unknownwith nothing to ever tell the reporter how to validate or clear it, so they go together.Nothing links to the template — no
template=5...URLs anywhere in the org, andconfig.ymldoes not reference it. Thepriority-supporthits inPricingTable.tsxandPricingCards.tsxare X pricing rows pointing at the legal SLA page, untouched by this.