You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.
Remove the errors when the output file path doesn't end in a particular extension (https://github.com/mholt/archiver/blob/master/targz.go#L40). As far as I can tell, these checks are just enforcing a file naming convention; I don't think they help ensure correctness. Seems like the extension checking could be made optional, ideally be decoupling it from the archive action.
Why is this feature a useful, necessary, and/or important addition to this project?
My project builds artifacts and puts them in a file store where the file names are the checksums.
What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
As a workaround, I'm writing to a tempfile with the required extension (.tar.gz, in my case) and then renaming the file to the checksum.
The text was updated successfully, but these errors were encountered:
What would you like to have changed?
Remove the errors when the output file path doesn't end in a particular extension (https://github.com/mholt/archiver/blob/master/targz.go#L40). As far as I can tell, these checks are just enforcing a file naming convention; I don't think they help ensure correctness. Seems like the extension checking could be made optional, ideally be decoupling it from the archive action.
Why is this feature a useful, necessary, and/or important addition to this project?
My project builds artifacts and puts them in a file store where the file names are the checksums.
What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
As a workaround, I'm writing to a tempfile with the required extension (.tar.gz, in my case) and then renaming the file to the checksum.
The text was updated successfully, but these errors were encountered: