ci: generate and display qr code in release notes - #38
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the tag-triggered release workflow to generate a QR code pointing to the tagged ZIP asset and include that QR code in the GitHub Release content, mirroring the existing pr_qrcode workflow approach.
Changes:
- Switch ZIP asset naming to use
${{ github.ref_name }}for tag-based releases. - Add a step to generate
qrcode.pngduring the release workflow. - Upload
qrcode.pngas a release asset and include an embedded image reference in the release content.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Guilhem Allaman <40383801+gounux@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Using similar mechanism than in the
pr_qrcodeworkflow,