Version Control
Save named branches, view history, compare changes, and restore previous versions of your paper.
Scriptora includes built-in version control for your paper. Every compile creates an autosave; you can also save named branches at any point to mark important milestones.
Saving a named branch
Click the Branch button (git icon) in the top toolbar. Type a name and press Enter.
Good branch names describe the state of the paper:
before-major-revisionssubmission-v1after-reviewer-2-fixescamera-ready
Save a branch before making any large structural change. If the change doesn't work out, you can restore instantly.
Viewing history
Click History in the left sidebar to see all saved versions and autosaves. Each entry shows:
- Branch name (or "Autosave")
- Date and time
- Who saved it
Versions are listed newest-first. Named branches are visually distinct from autosaves so you can quickly find milestones.
Restoring a version
Click any version in the history list, then Restore this version. The editor loads that version's files.
Your current work is automatically saved as a new autosave before the restore, so you won't lose anything — you can always go back.
Comparing versions
Click any version, then Compare with current to see a side-by-side diff. Changed lines are highlighted:
- Green — added lines
- Red — removed lines
This is useful for reviewing what changed between reviewer rounds or between draft iterations.
Autosaves
Scriptora autosaves your work every few minutes and after each compile. Autosaves appear in the history with a timestamp only (no name). You can restore any autosave just like a named branch.
Suggested workflow
Save a branch: "initial-draft".
Save: "submitted-to-nature". Now you have a snapshot of exactly what was submitted.
Save: "before-revision-1". Make your changes. When done, save: "revision-1-complete".
Use the diff view to compare "submitted-to-nature" with "revision-1-complete" and verify all reviewer points were addressed.