Repository navigation
Preserve cache exclusions through source-ledger creation - #62
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Inventory reports that exclude regenerable MO2 Python caches currently fail when passed to the source-ledger command. Accept the inventory's existing exclusion reason and retain the record through ledger creation and archive mapping.
The regression check exercises the actual inventory-to-ledger-to-mapping path, preserves included files and exclusions, and still rejects unknown exclusion reasons. It failed before the fix. Validation: Svelte check reports zero errors/warnings; the full suite passes 192 tests with one optional skip; git diff --check passes.