-
Notifications
You must be signed in to change notification settings - Fork 417
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
any-glob-all-files does not working intuitevely #731
Comments
Hi, @jnewb1 👋 Thanks for the issue and PR, we will take a look. |
Hi, @jnewb1, I believe that for your particular use case the glob's syntax of grouping conditions:
Could you, please, check that logic of this grouping is what you want to achieve and ping me back? |
Thank you, this syntax works for my use case, though I think it is less readable |
That that {} syntax documented anywhere? I couldn't find it. It's certainly not intuitive, and |
Despite its name, this atom acts like one-glob-to-all-files and a different syntax with braces must be used to get any-glob-to-all-files semantics. Unfortunately, this makes the file completely unreadable. Ref: actions/labeler#731
This test verifies that the glob brace syntax will match any glob against all files. Document that any-glob-to-all-files means any single glob. This reduces the ambiguity that caused actions#731 and other issues to be opened. Also, fix an any-glob-to-any-file example so it actually matches within the entire repository.
there is currently no way to apply the "CI" label with the following rule
any-glob-all-files: [Jenkinsfile, .github/**]
when a PR which changes both Jenkinsfile and github actions files
open PR to fix: #714
The text was updated successfully, but these errors were encountered: