Each release makes the demo video again, with the screenshots
A new website-media skill makes the screenshots and the website's demo video, says what to look at, and commits them: the screenshots in MeshTerm, the video in the site checkout. The release skill runs it after the bump and pushes the site before the tag, so the website job builds the page with the new video. The release preflight also reports the site checkout. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
507e3bd999
commit
daf16505d7
4 files changed
+222
-30
No files matched your search
+4
-2
@@ -103,5 +103,7 @@ something slow: the tiles of the map, and most of the read of the repeater's set
|
||||
Thus the video jumps over the wait.
|
||||
|
||||
Each run gives the same video to the eye, but not the same file, because the camera copies
|
||||
the screen on the real clock. After a change to the screens, run the script, then rebuild
|
||||
the website (refer to the README of the `meshterm.net` repository).
|
||||
the screen on the real clock. Each release makes the video again, after the screenshots,
|
||||
and pushes it to the website repository before the tag. After a change to the screens
|
||||
between two releases, run the two scripts, then rebuild the website (refer to the README of
|
||||
the `meshterm.net` repository).
|
||||
Reference in new issue
Block a user