fix: Issues with content filtering when using patterns #578
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
--
ZipContentFilter
logic for patterns that have a single allowed pattern.Earlier this would include all files.
--
generate_content_hash
also considers the patterns before generating thehash so that the hash generated matches the content of the zip.
Motivation and Context
[ ".*.py$" ]
will also include files that do not match that pattern.Breaking Changes
Unless someone is relying on the legacy behaviour this should not be a breaking change. It will however cause redeployments because of content hash changes.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request