Conversation
Github doesn't let me create a release with attached binaries and we currently have no atumation for adding binaries to tags/releases. So consider this a workaround until we get this fixed.
mikesperber
left a comment
mikesperber
left a comment
There was a problem hiding this comment.
The PDFs are directly pushed to public.isaqb.org, see note I just added to README.
I assume your requested changes are about not storing the PDFs as artifacts directly in the repo? I'm totally fine with removing that directory once we have proper PDF artifacts attached to the Releases. That's actually the cleaner solution. For now the directory is just a workaround to have something downloadable while we sort this out. The underlying purpose remains the same though: trainers need a stable, versioned PDF they can point participants to. "Latest" on public.isaqb.org is great for most purposes, but when I hand out exam questions that have been printed three weeks before a course, I'd like participants to be able to pull up the exact same version electronically - not whatever happened to be released in the meantime. GitHub Releases are also simply the place users expect downloadable artifacts in an open-source project. Tags tell developers something was versioned; Releases tell everyone else what to download. Please reconsider your request for changes. It's just a workaround. |
alxlo
changed the title
|
I cede to pragmatism, no release PDFs in the repo anymore. |
|
@alxlo Thanks for explaining what you need. Could you create an issue asking for Github releases and assign it to me? That should be very doable. |
2 participants
Github doesn't let me create a release with attached binaries and we currently have no automation for adding binaries to tags/releases. So consider this a workaround until we get this fixed.Only update the release version in the document to keep it in sync with the tag.