.gitallowed is scanned for secrets making ignoring specific secrets tedious...

if a file has a secret you can ignore the specific instance of it using a regular expression in the `.gitallowed` file

However as you want the exception to be as specific as possible - generally you do not want a generic regexp but a very specific one that will match the exact secret (to prevent any other secrets).

For example a README which contains an example of how to convert an rsa private key would have the line
` String s = "-----BEGIN RSA PRIVATE KEY-----\n"`

And so as you do not want to genericall allow any RSA key to be added you would add a lie like the following to `.gitallowed`
` String s = "-----BEGIN RSA PRIVATE KEY-----\\n"`

This is great and allows the secret to be ignored in the file, however there is an epic fail as now you can not commit as the `.gitallowed` file itslef is flagged as containing a match.

```
c:\workarea\myrepo >git commit -a -m "Add instructions for converting a key"
README.md:72: String s = "-----BEGIN RSA PRIVATE KEY-----\n"

[ERROR] Matched one or more prohibited patterns

Possible mitigations:
- Mark false positives as allowed using: git config --add secrets.allowed ...
- Mark false positives as allowed by adding regular expressions to .gitallowed at repository's root directory
- List your configured patterns: git config --get-all secrets.patterns
- List your configured allowed patterns: git config --get-all secrets.allowed
- List your configured allowed patterns in .gitallowed at repository's root directory
- Use --no-verify if this is a one-time false positive

c:\workarea\myrepo >echo String s = "-----BEGIN RSA PRIVATE KEY-----\\n"> .gitallowed

c:\workarea\myrepo >git add .gitallowed

c:\workarea\myrepo >git commit -a -m "Add instructions for converting a key"
.gitallowed:1: String s = "-----BEGIN RSA PRIVATE KEY-----\\n"

[ERROR] Matched one or more prohibited patterns

Possible mitigations:
- Mark false positives as allowed using: git config --add secrets.allowed ...
- Mark false positives as allowed by adding regular expressions to .gitallowed at repository's root directory
- List your configured patterns: git config --get-all secrets.patterns
- List your configured allowed patterns: git config --get-all secrets.allowed
- List your configured allowed patterns in .gitallowed at repository's root directory
- Use --no-verify if this is a one-time false positive
```

as the `.gitallowed` file is expect to have things that would trigger secret warnings (otherwise it would not need to contain them to supress them) this file should be excluded from scanning.

Start by reproducing the reported commit with a README.md example and the matching exception in the root .gitallowed file. Trace the secret-scanning entry point used by git commit, then verify that .gitallowed is excluded while the same pattern is still detected in README.md and the commit succeeds.

Written by the indexing model from the issue text.