Once a board is connected to a repository, each saved version is a GitHub Release — a tagged commit of the board files. You can save new versions, browse old ones, and import any release back into the board.
Save a version
In the GitHub dialog, under Save board to release:
- Optionally type a version (used as the release tag and name) and release notes. Leave them blank to auto-tag with a timestamp like
board-20260630-194812. - Click Save to release.
The app commits board.json, index.html, and the media/ folder to the repo’s default branch and tags a GitHub Release for that commit.
If nothing has changed since the last save, the app tells you *”No changes since the last release — nothing to save.”* and skips the commit.
Browse and import releases
The Releases panel lists every release in the repo (newest first), each showing its name, date, author, and a badge:
- App — saved from the GreenLight app.
- Agent — published by an external agent (see Agent-Built Boards).
- Current — this release matches the board you currently have open.
Pick an import mode, then click Import on a release:
- Replace — discard the current board and load the release exactly as saved. This is how you roll back to an earlier version.
- Append — add the release’s elements and arrows onto the current board, keeping what you already have.
Importing a release marked Current runs a force-import (the contents are identical, so the app would otherwise skip it).
“New release available”
When the repo has a release this board hasn’t imported yet, the GitHub toolbar icon shows a pulsing green dot and the dialog shows a New release available banner with an Import this release button. The app checks for new releases when you open the dialog and periodically in the background, so versions saved from another computer — or built by an agent — surface automatically.
Avoiding overwrites (stale-write guard)
If you try to Save to release while the repo already has a newer release you haven’t imported (for example, saved from another machine or by an agent), the app warns:
This repo has a newer release this board hasn’t imported.
You then choose:
- Import it first — pull the newer release in before saving, so nothing is lost.
- Save anyway — push your current board as the new working files. The newer release’s snapshot is kept in the repo’s release history; it is not deleted.
This guard makes multi-computer and agent workflows safe by default — you decide how to resolve a divergence instead of silently overwriting work.
Where to go next
- Agent-Built Boards — let an external agent publish releases.
- Connecting a Repository — token and repo setup.
Leave a Reply