Pro plan. Available on Pro and above, during the free trial, and in every self-hosted install.
Every change in Sitepins is a Git commit, which means every change is reversible. You don’t need a terminal to reverse one.
Recent Git Activities
The project overview page has a Recent Git Activities card listing recent commits, four at a time, with Load More for older ones.
Each entry shows:
- Who made the commit, with their avatar
- The commit message, linking to the commit on GitHub or GitLab
- How long ago it landed
- Its build status
Undo Commit
Undo commit reverses a single commit while leaving everything after it in place. Sitepins creates a new commit that undoes that one — your history stays intact and nothing is destroyed.
Use it when one specific change was wrong but later work was fine.
Undo commit is available for GitHub repositories only.
Restore Version
Restore version takes your branch back to the state it was in at a chosen commit. Everything committed after that point is undone.
The two providers behave differently, and Sitepins tells you which you’re about to do in the confirmation dialog:
| Provider | Behavior |
|---|---|
| GitHub | Hard reset to that commit. Later commits are removed from the branch. This is destructive and permanent. |
| GitLab | Creates a new commit that reverts back to that state. History is preserved. |
You can’t restore to the latest commit — there’d be nothing to do.
On GitHub, restoring an older version rewrites the branch. Commits made after the restore point are gone, including any made by teammates or pushed from outside Sitepins. Make sure nobody has unpushed work depending on them.
Who Can Do This
Restoring and undoing require the owner or admin role in the organization. Editors see the commit list but get “Only admins and owners can perform this action” if they try to act on it.
See Team & Roles.
Restore vs Reset
Two different things with similar names:
- Reset, in the editor header, discards unsaved changes in the current file. Nothing has been committed yet, so nothing in Git changes.
- Restore version and Undo commit operate on Git history and affect the whole repository.
If you haven’t saved yet, you want Reset. If you’ve already published, you want this page.
Recovering a Deleted File
Deleting a file in Sitepins is a commit like any other. To get it back, find the deletion commit in Recent Git Activities and Undo commit — the file returns with its content intact.
Seeing Full History
For anything beyond recent commits — comparing versions, browsing a file’s full history, cherry-picking — click through to GitHub or GitLab. Sitepins commits are ordinary commits, so every Git tool works on them.