fix: shorten output filenames with readable labels and hashes - #133
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
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.
Long target URLs and dataset names can make generated filenames unreadable or too long to create. Compact options now use up to 24 readable characters plus a 12-character SHA-256 suffix, replacing punctuation such as
=,/, and:with hyphens. Long dataset names and tags use the same helper; generated result and dataset filenames stay under 180 characters with their timestamps and extensions intact.Automatic resume uses the same naming logic and also recognizes existing filenames. Full options still reach the target unchanged. The change is limited to output naming, resume lookup, documentation, and regression tests.
Validation: