-
Notifications
You must be signed in to change notification settings - Fork 61
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
Exclude .wokeignore
file in scans
#243
Comments
👋 Thanks for submitting your first issue! Please be sure to read and follow our Code of Conduct and Contributing guide. ⭐️ Is your org or open source project using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: