Repository navigation
Add configurable image rename prefixes - #20
Merged
Merged
Conversation
HoungDev
marked this pull request as ready for review
August 7, 2026 09:39
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
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.
Summary
rename --prefixwhile preservingimageas the defaultSafety and compatibility
Invalid prefixes are rejected before files or manifests change. Validation covers empty or padded values, path separators, control and Windows-invalid characters, reserved device names, trailing periods, and filename-component length limits. Existing commands without
--prefixretain theimage_Nnaming format, and manifests remain version 1 because they already store concrete operations.Verification
ruff check .ruff format --check .pytest— 85 passed, 94.02% coveragepip-audit— no known vulnerabilitiestwine checkpassedCloses #17