Repository navigation
Capture release screenshots automatically in CI - #44
Merged
Merged
Conversation
The preview and tag jobs now run the common capture script on the emulator and compose one screenshot sheet for the release notes. Tag releases are always created fresh (the preview-to-tag conversion is gone), and the emulator smoke job is manual-only since the release jobs already exercise the demo build. Signed-off-by: dzid26 <dzidmail@gmail.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.
Simplifies releases back to the simple model: the common capture script runs in CI, and each release attaches what it produced.
.github/scripts/capture-screenshots.shon the emulator, and compose onescreenshot-sheet.png(light row + dark row).continue-on-error, and the notes skip the screenshot section when the sheet is missing).build-release-notes.shandscreenshot-sections.sh.demo-smoke's emulator job is manual-only (workflow_dispatch), since the release jobs exercise the demo build now.Net: no committed sheets, no pinned URLs, no fallback paths — one script, two call sites.