Custom pattern does not apply for filename

[perryzjc]

Describe the bug
The custom pattern can work for the file content but not for the file name.
It appears that this app is able to detect filenames, such as danger.pem. The example is here

Expected behavior
The custom pattern should also apply to the filename.

Desktop (please complete the following information):

• OS: macOS Big Sur v11.1
• Browser: chrome

[tinamthomas]

I'm curious to know more about the custom patterns you were looking for the file name to ignore. Do you have a few examples?

Are those file names very specific to your project, or are they more generic files names that could apply to other projects (and might make sense to add to the ruleset that the filenamedetector currently looks at)

[tw-owen-nelson]

Custom patterns apply specifically to file content. To configure talisman to ignore multiple files that it would normally mark as having suspicious filenames, add a fileignoreconfig that ignores the filename detector for all files matching your desired pattern.

For example, to allow all files ending in .env to be checked in despite having a 'suspicious' name, you could use the following .talismanrc:

fileignoreconfig:
- filename: *.env
  ignore_detectors: [filename]

Talisman would still scan the content of any files with names matching *.env for potential secrets, but it wouldn't flag the file based on just the filename.