use existing path matching logic when filtering allowed patterns on file configs #418

second-frank · 2023-02-27T16:10:29Z

Resolves #414

This PR adds the possibility to use allowed_patterns together with file path wildcards in the fileignoreconfig, while still allowing file specific checksum-based ignore configs - as printed by the githook reports.

For example, something like this would be possible:

fileignoreconfig:
- filename: 'sub-folder/*.yml'
  allowed_patterns: [key]
- filename: sub-folder/foo.yml
  checksum: a21f3d967b236bd1ae3d056323c7ee054ac63b2b374dd1864d8bba21169b2b33

The program was tested solely for our own use cases, which might differ from yours.
Frank Seidel frank.seidel@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH
Provider Information

…ile configs (thoughtworks#414) - requires to change ChecksumCompare too, so it considers all ignore configs (and not only the first matching one)

use existing path matching logic when filtering allowed patterns on f…

7ac7276

…ile configs (thoughtworks#414) - requires to change ChecksumCompare too, so it considers all ignore configs (and not only the first matching one)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

use existing path matching logic when filtering allowed patterns on file configs #418

use existing path matching logic when filtering allowed patterns on file configs #418

second-frank commented Feb 27, 2023

use existing path matching logic when filtering allowed patterns on file configs #418

Are you sure you want to change the base?

use existing path matching logic when filtering allowed patterns on file configs #418

Conversation

second-frank commented Feb 27, 2023