Skip to main content

Version Control

Every change in your Natively project is tracked as a commit, giving you full version history and the ability to revert if needed.

How It Works

Each time the AI makes changes to your code:
  1. Changes are made - Files are created or modified
  2. Build completes - App compiles successfully
  3. Commit created - Changes are saved with a descriptive message
  4. Preview updates - You see the result immediately

Viewing History

Access your version history:
1

Open History

Click the History icon in the sidebar or chat header
2

Browse Commits

See all commits with messages and timestamps
3

View Changes

Click a commit to see what files were changed

Commit Information

Each commit shows:
FieldDescription
MessageWhat was changed
TimestampWhen the change was made
Files ChangedList of modified files
Update NumberSequential version number

Reverting Changes

If something breaks, you can revert to a previous version:
1

Open History

Navigate to the version history panel
2

Find Working Version

Look for the last commit where everything worked
3

Revert

Click the revert button on that commit
4

Confirm

Your project is restored to that state
Reverting discards all changes made after the selected commit. Use carefully.

Via AI Chat

You can also ask the AI to revert:
Revert to the previous version - the last change broke navigation.
Undo the last change to the home screen.

GitHub Sync

With GitHub connected, your version history is also:
  • Backed up to your repository
  • Accessible via standard Git tools
  • Shareable with collaborators

GitHub Integration

Learn about GitHub sync

Best Practices

Test Before Moving On

Verify each change works before making more

Note Important Versions

Remember which commits represent major milestones

Revert Early

If something breaks, revert quickly rather than trying to fix forward

Read Commit Messages

The AI’s commit messages describe what changed

Understanding Changes

What Gets Committed

  • Source code changes
  • New files and assets
  • Configuration updates
  • Package dependency changes

What Doesn’t Get Committed

  • Chat history (stored separately)
  • Environment variables (stored securely)
  • Build artifacts (regenerated each time)