Save vs Commit

Goal: Understand the two-stage flow for changes.

OpenX uses a git-like flow: save your work as a draft, then commit to deploy. This keeps accidental changes out of production.

The two stages

Stage	What happens	Who sees it
Save	Stored as a draft	Only you
Commit + Deploy	Goes live	Everyone

Why two stages

• Safe experimentation - try changes without touching what's live; revert easily.
• Confidence - every commit is recorded, reviewable, and attributable.
• Collaboration - teammates can hold their own drafts without conflicts, and merge when ready.

Save a draft

When you change anything - a connection, surface, or warm query - the Save icon glows to show you have uncommitted changes. Drafts persist across sessions: close the browser, come back later, your work is still there.

Commit and deploy

1. Click the Save icon - your changes are committed to the workshop
2. When the green check appears near Deploy, click it to push live
3. Deploy takes a moment and runs in the background - keep working

Or ask Azi: "Commit my changes with the message 'Added signup alerts'." She packages and deploys it.

What gets committed

Resource	Committed
Connection configs	yes
Surface definitions	yes
Warm query code	yes
API configurations	yes
Role assignments	yes

Not committed: runtime data, logs, metrics.

History

Open the History icon to see every commit - who, when, what changed, and the message. If something breaks, you can trace exactly what changed and who changed it.

Revert

• Discard a draft - click the draft indicator, choose Discard Changes, confirm.
• Revert a commit - in History, find the commit, click Revert. This creates a new commit that undoes it.

Best practices

Practice	Why
Save often	Don't lose work
Clear commit messages	Easier-to-read history
Small commits	Easier to revert
Review before committing	Catch mistakes early

Next steps

• Tour the interface -> Navigation
• Set roles -> Permissions
• Build a query -> Warm Queries