Version Control

Version Control

iSparkClaw AI Editor includes built-in version control for tracking changes and reverting to previous versions of your documents.

Git Status

The status bar shows the current version control state:

• Git indicator — Shows when Git is active
• Branch name — Shows your current branch (e.g., main, develop)

Initializing Version Control

When you create a new workspace, version control is set up automatically.

For existing projects:

1. Click the Git button in the header
2. Select Initialize Repository
3. Version control is ready to use

Viewing History

Click Git → History to see all changes:

Each entry shows:

• Date — When the change was made
• Description — What was changed
• Author — Who made the change

Creating Checkpoints

Save your progress by creating checkpoints (called commits):

1. Click Git → Commit in the header
2. Write a description of your changes
3. Select which files to include
4. Click Commit

Viewing Changes

Select a commit and click Show Diff to see what changed:

• Green text — New content added
• Red text — Content removed
• White text — Unchanged content

Reverting Changes

Restore Previous Version

1. Select a commit in history
2. Click Rollback
3. Confirm the action

Note: This will restore the file to that point in time.

Safe Revert

Create a new commit that undoes changes:

1. Select a commit
2. Choose “Create revert commit”
3. A new commit reverses the changes

This keeps your history intact.

Branching

Branches let you work on new features without affecting the main work.

Creating a Branch

1. Click Git → Manage Branches
2. Click Create Branch
3. Enter a name (e.g., “new-feature”)
4. Click Create

Switching Branches

1. Select a branch from the list
2. Click Switch
3. Your work updates to that branch

Note: Save your work before switching branches.

Saving Work Temporarily

Stash lets you save work without committing:

1. Click Git → Stash Changes
2. Add a description
3. Your changes are saved temporarily

To restore:

1. Click Git → Pop Stash
2. Your saved work returns

Best Practices

• Create checkpoints before major changes
• Write clear descriptions for your commits
• Use branches for new features
• Stash work before switching branches