Version Control

Every change to your files is tracked automatically with complete version history.

How Version Control Works

Contextium automatically creates a new version whenever:

• You save changes to a file
• A file is restored from trash
• Content is modified via API

Each version captures:

• Complete file content
• Who made the change
• When it was changed
• Change summary
• Diff from previous version

Viewing Version History

Access Version History

1. Open any file
2. Click History in the sidebar
3. View all versions in chronological order

Version Information

Each version shows:

• Version Number - Sequential number (v1, v2, v3...)
• Author - Who made the change
• Timestamp - Exact date and time
• Change Summary - Description of what changed
• Diff - Line-by-line comparison

View a Specific Version

Click any version to see:

• Full content at that point in time
• Diff compared to previous version
• Version metadata

Comparing Versions

View Changes

The diff view highlights:

• Green lines - Added content
• Red lines - Removed content
• Unchanged lines - Context around changes

Compare Any Two Versions

1. Open version history
2. Select first version
3. Click Compare
4. Select second version
5. View unified diff

Reverting to Previous Versions

Restore a Previous Version

1. Open version history
2. Find the version you want to restore
3. Click Restore This Version
4. Confirm restoration

Restoring creates a new version with the old content. Original history is preserved.

Why Revert?

Common reasons to restore previous versions:

• Undo unwanted changes
• Recover accidentally deleted content
• Return to a known good state
• Compare different approaches

Version Retention

How long versions are kept depends on your plan:

• Starter - 7 days
• Professional - 30 days
• Business - 90 days
• Enterprise - Unlimited

After retention period expires, older versions are automatically deleted to save storage.

Change Summaries

Automatic Summaries

Contextium generates summaries for changes:

• "Updated authentication section"
• "Added new API endpoint documentation"
• "Fixed typos in introduction"

Manual Summaries

When making significant changes:

1. Save your file
2. The new version appears in history
3. Click Edit Summary on the version
4. Enter a custom description
5. Click Save

Good summaries help you and your team understand changes at a glance.

Version Control Best Practices

Save Frequently

Auto-save runs every 30 seconds, but manual saves with Cmd/Ctrl + S:

• Create clearer version checkpoints
• Make history easier to understand
• Enable easier rollback to specific points

Write Good Summaries

For major changes, add custom summaries:

• ✅ "Restructured API authentication flow"
• ✅ "Added error handling examples"
• ✅ "Updated deprecated endpoint info"
• ❌ "Changes"
• ❌ "Update"
• ❌ "Edit"

Review History Regularly

Before making major changes:

1. Review recent version history
2. Understand what changed
3. Coordinate with teammates
4. Avoid conflicts

• New version is created automatically
• Shows who approved it

Audit Trail

Version history provides a complete audit trail:

• Who changed what and when
• Full content at every point in time
• Attribution for all contributions
• Basis for compliance requirements

Business and Enterprise plans include enhanced audit logs.

API Access to Versions

Access version history programmatically:

# Get version history for a file
curl -X GET "https://api.contextium.io/files/{fileId}/versions" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Get specific version content
curl -X GET "https://api.contextium.io/files/{fileId}/versions/{versionId}" \
  -H "Authorization: Bearer YOUR_API_KEY"

See API Documentation for full reference.

Version Storage

Versions count toward your storage quota:

• Each version stores full file content
• Storage = sum of all versions of all files
• Monitor usage in Settings → Usage
• Consider retention limits if storage is constrained

Next Steps

• Add comments to versions
• Restore files from trash
• Access API documentation