Rollbacks

A rollback lets you undo a commit by creating a new commit that reverses its changes. History is never erased — the original commit and the rollback both remain in the log.

How rollbacks work

Specor’s rollback is non-destructive: rather than deleting or mutating past commits, it calculates the inverse of a commit and applies it as a new commit on top.

For example, if commit A added a Feature called “Split Payment”, rolling back A creates a new commit B that removes that Feature. Both A and B are visible in history.

This means:

• You can always see what was rolled back, by whom, and when
• You can roll back the rollback (by rolling back commit B)
• No data is permanently lost

Rolling back a commit

1. Open the History view (clock icon in the left sidebar)
2. Find the commit you want to revert
3. Click the commit to expand it
4. Click Rollback this commit (the rotate-left icon)
5. Review the rollback preview — a diff showing exactly what will be reversed
6. Optionally add a note explaining why you’re rolling back
7. Click Confirm rollback

A new commit appears in history labelled Rollback: <original commit name>.

The rollback preview

Before confirming, Specor shows you a full preview of what the rollback will do:

• Nodes that will be removed — nodes that were created in the original commit
• Nodes that will be restored — nodes that were deleted in the original commit
• Fields that will be reverted — field-level changes undone

If the rollback would leave the graph in a broken state (e.g. because other commits have since added edges to nodes that would be deleted), Specor will warn you and let you decide whether to proceed.

Blocked rollbacks

A rollback may be blocked if subsequent commits have built on top of the commit you’re trying to revert in a way that can’t be cleanly undone. In this case, Specor shows you the exact conflicts that would result.

If a rollback is blocked, your options are:

• Roll back the more recent commits first, then retry
• Use the graph editor to manually undo the specific changes instead

Rollback vs. editing manually

Approach	When to use
Rollback	Revert an entire commit cleanly — works best when changes are self-contained
Manual edit	Undo specific parts of a change while keeping others

History after a rollback

Both the original commit and the rollback commit appear in the history log. You can diff them, inspect what changed, and see who did the rollback and when. The complete audit trail is always preserved.