Tasks
Version history
Every change to an app is a numbered version — see what changed, jump to the message that caused it, name and bookmark the good ones, and restore any of them without losing what came after.
An app changes every time you ask for something. Each of those changes is a version, kept with who made it and when, so a bad turn is never expensive.
Open it from the clock icon in the app pane header.
What a version records
| Column | What it tells you |
|---|---|
| Number | Version 1 is the first build; every change since then is the next number |
| Author | You, or the assistant that made the change |
| When | Relative time, in your own calendar and clock |
| Restored from | Marked when the version was made by restoring an older one |
What you can do with one
See what changed. A file-by-file diff of that version against the one before it — added, removed and edited lines.
Go to the message. Jumps back to the point in the conversation that produced the version, so you can read what was asked for and continue from there.
Name it. Give a version a label — “before the pricing rewrite” — instead of remembering a number.
Bookmark it. Bookmarked versions get their own tab, so the two or three that matter do not get lost among fifty small edits.
Restore it. Puts the app’s files back to that version.
Restoring does not erase anything
A restore is recorded as a new version on top of the history, marked as restored from the one you chose. Everything that happened in between is still there, and you can restore forward again just as easily.
Restoring and the published app
Restoring changes the app you are working on. The version people can open on the internet stays exactly as it was until you press Publish again — so you can roll back, look around, and decide, without visitors seeing anything move.
If you are about to try something ambitious, bookmark the version you are happy with first. It costs one click and turns “can we get back?” into a question with an obvious answer.