Skip to content

View snapshots and milestones

The Snapshots tab shows the repository's published snapshot history, read from .gitm/builds.jsonl. Each snapshot is a whole-repo milestone published from GitM; because snapshots are deliberate milestones, the list shows fewer, more meaningful entries than a per-edit log. Managers and admins can also mark milestones.

Prerequisites

  • Signed in and connected to a repository.
  • At least one snapshot has been published from GitM.

See snapshots

  1. Open the Snapshots tab.
  2. Snapshots are listed with their number, author, time, and description.
  3. Use the search box to filter the list.

Milestones (from .gitm/milestones.json) are shown against their snapshots.

Per-file cloud versions. Each file row shows a read-only Cx badge (e.g. C3) — the number of distinct cloud versions of that file. GitMCloud computes this the same way GitM does (distinct content, identical bytes don't add a number), so the two apps always agree. GitMCloud has no local (Lx) versions, no "you are here" pointer, and no Restore — those need the add-in.

Mark a milestone

Marking a milestone flags a snapshot as significant and writes a note to .gitm/milestones.json.

  1. Find the snapshot on the Snapshots tab.
  2. Choose Mark Milestone and enter a note.

Permission: marking/editing milestones is a write action. It is available to Manager-level roles and above — see Roles and permissions.

Expected result

  • The snapshot list reflects what GitM has published.
  • A marked milestone appears against its snapshot and is visible to GitM and other GitMCloud users (it's committed to the repository).

Troubleshooting

Symptom Cause Fix
No snapshots shown None published yet, or wrong branch selected. Publish from GitM; check the branch in Settings → Connection.
Can't mark a milestone Your role is below Manager. Ask an admin, or get a higher role.
A new snapshot isn't showing GitMCloud reads the branch you connected to. Confirm the snapshot was pushed to that branch; refresh.

Known limitations

  • GitMCloud reads whatever branch you connected to; it does not aggregate across branches.
  • Snapshot history is the list in .gitm/builds.jsonl; GitMCloud does not rewrite or reorder it.