Skip to main content
Fimo keeps a full history of your project so you can go back if something goes wrong. Because a Fimo project is real git plus a versioned content plane, history covers both code and content together.

​
What’s tracked

  • Code — your project is a genuine git repository with fimo as the remote. Every fimo deploy commits and pushes, so your code history is standard git history you can inspect, diff, and revert with git itself.
  • Releases — each production release is tagged. fimo publish --version <ver> tags main@HEAD as release/<version>, giving you named, restorable points in time.
  • Content — schemas, entries, labels, assets, and forms are versioned per environment alongside the code that renders them.

​
Restore an earlier state

Point-in-time restore that rolls content and code back together lives in Fimo Studio’s version history — the safest way to recover a whole-project state without wrangling git and the content plane by hand.
Want to explore a rollback without touching the live site? Create an isolated environment first (fimo checkout -b restore-test), verify it, then merge and publish. See Environments.

​
What’s next

Version history in Studio

Restore a whole-project state visually.

Environments

Isolate risky changes on a branch.

Deploy & publish

How releases are cut.