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.
Which issue does this PR close?
Related to #6880
Rationale for this change
When we were testing merge queues for this repo, I made all "rust test" steps mandatory. However, those "rust tests" weren't running for PRs that change documentation only - and as a result it was impossible to merge those PRs: #17183 (comment)
GitHub doesn't have a way to pair merge queues with
paths-ignore: https://github.com/orgs/community/discussions/45899 - so I had to move those checks to a separate step (this is how this problem is solved by the community).I'm using
dorny/paths-filteras it has already been approved by ASF and it is desired for us to use it.You'll notice
predicate-quantifieris marked as an unsupported arg:This arg is actually used, just not defined in the action definition. Once a release with dorny/paths-filter#279 is created, we'll switch to the new version and the warning will go away.
What changes are included in this PR?
A new action,
rust-required-checks, that will become mandatory (requirement to enable merge queues):Are these changes tested?
Yes:
Are there any user-facing changes?
No