You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to match all files with the .yml extension. Some are contained in hidden directories that are arbitrarily nested. Eg:
path/to/.hiddenDir/file.yml
or
path/to/.hiddenFile.yml
Neither case above would be captured by the **/*.yml path in my include config.
Request
Please allow for more flexible matching of hidden files & directories. For example, node-glob supports an option to treat dots as normal characters, which would make it trivial to handle the situations above using a single pattern instead of multiple variations that require knowledge of the directory structure. I'd like for file extension matching to be agnostic of directory structure so that license checking isn't accidentally missed in newly added areas of the repo.
Thanks!
The text was updated successfully, but these errors were encountered:
### Summary
I noticed we aren't enforcing license checking on any of our GitHub
workflow files. The reason is that the generic glob pattern we're using
(`**/*.yml`) doesn't match anything in hidden directories. I submitted a
feature request
[here](viperproject/check-license-header#350)
to make this more flexible. In the meantime, explicitly list out
`.github` in the config.
### Test Plan
* update the config first, see the license check
[fail](https://github.com/aurora-opensource/au/actions/runs/3857899619/jobs/6575810317)
for `clang-format-lint`
Problem
I'm trying to match all files with the
.yml
extension. Some are contained in hidden directories that are arbitrarily nested. Eg:or
Neither case above would be captured by the
**/*.yml
path in myinclude
config.Request
Please allow for more flexible matching of hidden files & directories. For example,
node-glob
supports an option to treat dots as normal characters, which would make it trivial to handle the situations above using a single pattern instead of multiple variations that require knowledge of the directory structure. I'd like for file extension matching to be agnostic of directory structure so that license checking isn't accidentally missed in newly added areas of the repo.Thanks!
The text was updated successfully, but these errors were encountered: