[Rpm-maint] [rpm-software-management/rpm] Automate tarball deployment with GitHub Actions (Issue #2702)

[Michal Domonkos]

Based on a separate discussion with @pmatilai, let's go with separating the documentation artifacts (html files generated with pandoc) into a tarball on its own, and upload that (via a GitHub action) to the given GitHub release so that it shows as an additional "asset". Bundling the documentation was just a convenience thing for packagers but it really isn't necessary as long as we provide the tarball alongside.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2702#issuecomment-2650832991
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/2702/2650832991 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20250211/264ba67c/attachment.htm>