[support-infra] Add synchronize to workflow triggers#19342
Merged
michelengelen merged 1 commit intoAug 26, 2025
Merged
Conversation
|
Deploy preview: https://deploy-preview-19342--material-ui-x.netlify.app/ Bundle size report
|
JCQuintas
approved these changes
Aug 26, 2025
synchronize to workflow triggerssynchronize to workflow triggers
Member
|
Nice 👍, the CI is tied to a commit, so it needs to run on each. With the initial GitHub Action (mui/material-ui#32886), we did https://github.com/mui/material-ui/blob/41da88f24d0c2a2ccb5480a95d352a6650607080/.github/workflows/check-if-pr-has-label.yml#L5, but this is a fork of https://github.com/mheap/github-action-required-labels?tab=readme-ov-file#complete-example, which does it correctly like in this PR. I have updated mui/mui-public#206 to flag that |
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.
The check type label workflow did not get triggered on updates to the PR HEAD, so it was stuck in an unresolved state.
This should fix it.