-
Notifications
You must be signed in to change notification settings - Fork 3.5k
CI: Various improvements to ci.yml #14996
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
base: main
Are you sure you want to change the base?
CI: Various improvements to ci.yml #14996
Conversation
Avoid unnecessary checks for certain jobs.
|
Hi @eksperimental, I am not planning to go ahead with those changes for now.
Thanks, |
|
|
||
| pull_request: | ||
| paths-ignore: | ||
| - "lib/**/*.md" |
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.
Is there a reason we are adding these?
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.
changes in the these files will not check the building of docs with warnings as errors.
You can introduce warnings in documentation, and it will never checked by the CI
|
I reopened the PR because we should merge the path changes. Is there a way to only run the docs one when only those files change? 🤔 |
|
That was the original reasoning behing moving the doc building to its own action. There's an action that can filter paths on a job/step level, its this one: https://github.com/dorny/paths-filter |
|
Yeah, I understand now it was the original rationale but we change the code more often than we change those pages, so optimizing for faster general changes is better. I guess we could run some git command that aborts the other runners, except the docs one, if the diff only lists those directories? |
|
Yes. detecting changes with |
|
I tried to implement a solution using |
|
Since you did the work, please do send a PR! Worst case scenario it will work for documentation purposes! |
|
I have a working version that uses |
Related PR: #14985