-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[code-infra] Use the same CI names on master & next #43064
Conversation
Netlify deploy previewhttps://deploy-preview-43064--material-ui.netlify.app/ Bundle size report |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't aware there was a list of required jobs somewhere.
Where can I find it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is under https://github.com/mui/material-ui/settings/rules/549978. I am not sure what are the roles that have access, but there is a ruleset that sets the require status check to be passed, e.g.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, it's defined on GitHub 👍🏻
I don't have access, but it's good to know where it's defined, thanks!
Cherry pick of (#42690)
We need to apply the change of renamed CI checks on master too, as we are using the same rules for master & next in terms of required checks. Without this change, we continued to see pending checks on master, as the checks with the new names don't exist on this branch.