Undo and restore

Versions

A version is a photograph of every code file in your project, taken when an AI generation succeeds.

Only a generation creates a version

Nothing else does. Not Ctrl+S, not a deployment, not an edit in the editor. One exception is automatic: MaShop photographs the current state just before a restore.

A project edited mostly by hand therefore shows an almost empty timeline. That is the rule, not a fault.

What a line tells you

• the word Generation, followed by seven characters of the repository commit;
• how long ago it ran;
• the number of files it holds;
• the credits billed for that generation.

A version holds the complete file tree, not only what changed. View diff compares it with the version before it. On the first version there is nothing to compare.

What restoring does

MaShop asks for confirmation, and warns that unsaved changes in the session will be lost. Then, in order:

• it photographs the current state under the name Before restoring, so the rollback is itself reversible;
• it replaces the workspace files in a single transaction, so a failure never leaves the workspace empty;
• if that version carries a commit, it writes a new commit on your GitHub with the restored content.

History on GitHub is not rewritten. The restore adds a commit, it erases none.

What restoring does not do

• It does not update your live site. Click Update afterwards, or nothing changes for your customers.
• It does not touch your database, your products, your orders, your customers or your images.
• If the write back to GitHub fails, the restore is still reported as a success. The failure only appears in the response.

Do not count on a version to undo a database change. Snapshots hold code files only. Restoring past a migration puts back code that talks to a database which has moved on.

Limits and cost

Restoring costs zero credits. It is capped at ten restores per minute. An empty timeline reads No snapshot yet.

Undo is not delete

Restoring is reversible by design. Deleting a project is not, and it does not remove everything the confirmation screen claims. That is covered on Publishing.