-
Notifications
You must be signed in to change notification settings - Fork 230
CI: Fix Skipped Required Workflows (again) #5907
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
CI: Fix Skipped Required Workflows (again) #5907
Conversation
| schedule: | ||
| - cron: "27 3 * * 0" |
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.
Removed cron schedule for CodeQL workflows (on Sundays at 3:27 AM...?).
5d8923f to
a6a94e4
Compare
|
The latest bug fix seems to have worked, if you look at the CI output for 705fd1a. I will push one more commit to resolve the point
mentioned in the PR description (this new commit will trigger CI, as expected), and then I think we could merge and test right away in #5883 (which is a docs-only PR), after rebasing that PR on |
Follow up on BLAST-WarpX#5889 and fix the issue that appeared in BLAST-WarpX#5883, related to the fact that we add the `clang-tidy` checks automatically from a matrix, rather than manually as separate jobs in the workflow file. Note that I had managed to fix a similar issue in the alternative in-house implementation I had proposed in BLAST-WarpX#5469. To-do: - [x] Fix main issue by applying the `if` condition at the `step` level (rather than the `job` level) - [x] Remove `cron` schedule for CodeQL workflows (on Sundays at 3:27 AM...?) - [x] Revert change in .github/workflows/check_changes.yml (implemented only to test the PR) Future PRs: - Skip also CodeQL workflows (C++ and Python files analysis) - not working yet...
Follow up on #5889 and fix the issue that appeared in #5883, related to the fact that we add the
clang-tidychecks automatically from a matrix, rather than manually as separate jobs in the workflow file.Note that I had managed to fix a similar issue in the alternative in-house implementation I had proposed in #5469.
To-do:
ifcondition at thesteplevel (rather than thejoblevel)cronschedule for CodeQL workflows (on Sundays at 3:27 AM...?)Future PRs: