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
If there is a file/path that includes a sensitive term in .wokeignore file, it will produce a warning. It seems like the intent of the file itself is to be ignored. For example, with the following .wokeignore content:
blacklist.jpg
Running woke produces the following output:
.wokeignore:1:0-9: `blacklist` may be insensitive, use `denylist`, `blocklist`, `exclusion list` instead (warning)
blacklist.jpg
To actually ignore these filenames, one must place .wokeignore itself in the .wokeignore file:
.wokeignore
blacklist.jpg
This is surprising behavior. Is it intended?
The text was updated successfully, but these errors were encountered:
If there is a file/path that includes a sensitive term in
.wokeignore
file, it will produce a warning. It seems like the intent of the file itself is to be ignored. For example, with the following.wokeignore
content:Running
woke
produces the following output:To actually ignore these filenames, one must place
.wokeignore
itself in the.wokeignore
file:This is surprising behavior. Is it intended?
The text was updated successfully, but these errors were encountered: