Switch to bash glob matching which should be more user friendly #150
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I brought in the suggestion for an ignore pattern in #70 and made a proof of concept which was integrated by @tehniemer.
As seen in #144 the pattern is hard to get right and does not follow the typical file globbing pattern rules.
I suggest a switch to bash file globbing patterns which are what linux users are probably used to. This does not need any new dependencies, but breaks the regex patterns in use (only released under beta so far). I also added a note for the documentation, that this feature should not be used to exclude often changing files (which will break parity calculations).
Fixes #144
I've tested the functionality in a separate script with some old log files from earlier runs and with a few runs on my own instance.
Type of change
Checklist: