[hotfix][ci] Ignore GHA build on non-code changes#28105
Merged
Conversation
Collaborator
fhueske
approved these changes
May 4, 2026
Contributor
fhueske
left a comment
There was a problem hiding this comment.
Thanks for the fix.
LGTM
| - 'docs/**' | ||
| - '**.md' | ||
| - '.gitignore' | ||
| - '.gitattributes' |
Contributor
There was a problem hiding this comment.
nit suggestion: I think LICENSE/NOTICE and .asf.yaml are also safe to ignore and might fit here
Contributor
Author
There was a problem hiding this comment.
I was thinking about it however the answer is no
the reason is that RAT license check in compile.sh parses them
and changes in LICENSE/NOTICE might lead to failure
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.
What is the purpose of the change
Do not start GHA bulid on non code changes
Brief change log
ci.yaml
Verifying this change
GHA
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation
Was generative AI tooling used to co-author this PR?