Repository navigation
Refresh screenshots when a release is published - #88
Merged
Merged
Conversation
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.
Moves the release bot from the daily canary to releases, as requested. After a tag release publishes, the build job commits the freshly captured PNGs into \website/images/\ on main as \github-actions[bot], only when a file differs. The daily \demo-smoke\ goes back to being a pure canary (capture + assert + artifact, no commits).\n\nOrdering: the refresh runs after \Release on tag, so a failed release never moves the website. \website/**\ is ignored by Android CI, so the commit only triggers the Pages deploy.\n\nRisk to note: if main is protected against direct pushes, this step will fail; in that case we switch the bot to open a PR instead. Review before merge.