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.
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
[core] Add
react-next
workflow in CircleCI #13360[core] Add
react-next
workflow in CircleCI #13360Changes from 10 commits
917e2f2
8d27ad0
0408bbb
7dc4fe2
54a6230
89949e6
f977295
43e241b
4eb5302
a561095
1a56356
c4751d1
1143436
8e294ae
eafbe98
02c00ea
dbee72a
738075a
8d92d02
ab80af3
d312393
0d12ad1
7a85c12
a8be510
5d2e392
f5689b7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The downside is that all the PRs will have a pending check if this workflow is not triggered manually.
An alternative approach that avoids the pending check is to manually trigger the workflow:
Screen.Recording.2024-06-05.at.21.08.20.mov
Thoughts?
cc @mui/code-infra
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 guess you could set up a nightly build, but then I suppose we have the problem of not being notified. I'm not sure how hard it would be to set up slack or email notifications for a single failed workflow.
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.
Yes, a scheduled workflow is good. But I also wanted to add an ability to run the workflow on the PR on demand.
This would be useful when working on React 19 compatibility, or when we want to make sure the specific PR would work across different React versions.
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.
Yep, I understand. Having those builds in pending state won't be the greatest DX though.
How hard would it be to do this workflow in GitHub actions? It would open up the possibility to build based on e.g. a PR comment, or PR title, or a label.
edit: ok, nvm, it's a lot of work
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.
Actually, triggering a CircleCI workflow from GitHub action if the PR has a specific label shouldn't be that hard to do 🤔
I've never used GitHub Actions, but I can give it a try, thanks for the suggestion 👍🏻
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.
Yes, it's a no-go. CircleCI is not great when it comes to optional manual workflows
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 don't think we get this info in the the pipeline, but I only investigated it briefly.
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've reverted the approval type for this workflow.
It is still possible to run react-next tests on demand, it's just not as convenient. See https://github.com/cherniavskii/mui-x/blob/react-19-in-CI/test/README.md#next-version
The upside is that the always pending workflow is gone 👍🏻
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.