Thanks (for the link, too)!
Indeed. We're currently
[thinking](https://github.com/rpm-software-management/rpm/issues/2702) of doing
that with an action that triggers on release creation (done manually or via `gh
release create` perhaps), creates a tarball from the given tag (basically with
`git archive`) and attaches it to the just-created release as an additional
asset (with `gh release upload`).
I've seen this
[done](https://github.com/containers/podman/blob/2e36bc0a05db4063e0436da5c6f413cfdfb909b4/.github/workflows/release-artifacts.yml#L194)
in your other project (podman), actually 😄, and did a quick PoC in my fork of
rpm, it works as expected.
This is based on the assumption that we don't want to rely on the default
tarballs provided in a GH release as it looks like they might be done on the
server dynamically (upon downloading), which I guess is also the reason you're
doing the above.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3565#issuecomment-2654959209
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3565/2654959...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
https://lists.rpm.org/mailman/listinfo/rpm-maint
