Skip to content

Open an earlier version

You can go back to an earlier state — to review an old design or recover something that changed. GitM gives you two scopes:

  • A whole snapshot — reset your entire project to a published snapshot, on the Snapshots tab.
  • A single file — bring just one file back to one of its versions, from that file's right-click Show Versions overlay.

See the history

  • Whole repository: open the Snapshots tab. Snapshots are listed newest-first with author, time, description, and a short commit id.
  • One file: in the Files tab, right-click the file → Show Versions. An overlay opens showing that file's timeline — its cloud versions (Cx) and any local versions (Lx), newest first, each with its own Restore.

The file's row also shows where it currently is as a Cx · Lx badge (e.g. C3 = on cloud version 3; C3 · L2 = two local versions on top of C3).

Restore a whole snapshot

  1. On the Snapshots tab, find the snapshot you want.
  2. Click Restore this Snapshot on that snapshot's row.
  3. GitM resets your whole working project to that snapshot. A banner explains that files were restored and that you can review and publish again from here.

Restore a single file

  1. Right-click the file → Versions.
  2. Find the version you want in the overlay.
  3. Click Restore on that version's row. Only that file changes; everything else is left untouched. The file becomes editable so you can review and check it in.

Open a snapshot on GitHub

Click GitHub on a snapshot's row to open that commit on github.com in your browser.

Expected result

  • Restore brings the chosen state into your working files so you can inspect or re-publish.
  • It is non-destructive — it does not rewrite history. You move forward by checking in (single file) or publishing a snapshot (whole repo) again.

Troubleshooting

Symptom Cause Fix
Brief flicker / thin line under the search box Cosmetic loading indicator. None needed.
Restore this Snapshot changed files you didn't expect A snapshot is a whole-repo capture; restoring it affects the entire working tree. Review the restore banner; use Get Latest to return to the newest state, or restore a single file instead.
A restored file is a placeholder Restore changes versions, not local bytes. Make it available.
The Cx badge looks wrong in Lightweight mode Version coordinate needs the file's true content on disk. Make the file available; the badge is exact once the real bytes are present.

Known limitations

  • Restore this Snapshot changes your whole project. Understand which snapshot you're restoring to before clicking; to undo, restore a different (e.g. the latest) snapshot or Get Latest.
  • History is shown as a linear newest-first list, not a branch graph.
  • Side-by-side compare of two arbitrary versions is limited; the supported flows are Restore and the GitHub link.