The current `.gitleaksignore` is cumbersome for ignoring directories already excluded by `.gitignore`. The user requests support for `.gitignore` syntax within `.gitleaksignore` or an option to use `.gitignore` directly to avoid redundancy and maintenance issues.
The 'dir' command is finding things that are not issues, but that I do not want to define in .gitleaksignore because it is too cumbersome. Here is an example where a js library in my project is giving multiple warnings from a directory that is ignored in '.gitignore' so will never be added to git. Adding these rules would clutter my ignore file and if I do a minor version update to the library it may change the location and require me to update it: ``` Finding: ...:this.authStore=new LocalAuthStore,this.collections=new CollectionService(t... Secret: this.collections=new RuleID: generic-api-key Entropy: 3.521928 File: .angular/cache/21.2.1/groceries/vite/deps/pocketbase.js.map Line: 4 Fingerprint: .angular/cache/21.2.1/groceries/vite/deps/pocketbase.js.map:generic-api-key:4 ``` This file is only used during the build process or when developing locally and will never make it into my git repository. I like to do 'gitleaks dir -v' prior to staging m