-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: provide package files directly, not as zip files #271
Comments
its because thats how github's workflows attach artifacts. we don't really have control/an easy solution for that without some heavy customization of artifact attachments, which is beyond my knowledge atm. |
You should be able to attach arbitrary files. As in, save it from the build workflow, then download in the release workflow. Obviously I have no idea what you guys’ workflow is in general and if that’s feasible or if you have some other constraints. |
I tried this once before and was not successful. Our workflow files are here: |
The constraint we're dealing with is specifically with Github's upload artifact workflow. See actions/upload-artifact#426. I don't see this as a big problem, but if users want the "naked" resources, then they must use the Github API. However, if we want to change this and continue to have things automated, one way if is to automate the Github release and use the |
I noticed that for the last couple releases the various distribution packages have come zipped up instead of the “naked” packages being attached to the release.
I’m assuming there is a reason for it, but running
dnf install <url>
is way more convenient than downloading an archive, unpacking it, and only then installing it :)The text was updated successfully, but these errors were encountered: