Source control
Source Control is Studio's built-in git client, a Navigator panel that records your work as commits and keeps your copy of the project in sync with its repository. Open it by clicking Source Control in the Project group of the Navigator rail, or with ⌘3 ; a badge on the button counts the files that have changed. It is a project-level panel: its header reads SOURCE CONTROL · project , and the badge stands whether or not a document is open.
If the project isn't tracked by git yet, the panel explains what source control buys you and offers Initialize Repository to start tracking it locally, or Create GitHub repository to go straight to a hosted one. See GitHub . Projects created from the New Project wizard are already tracked, so you'll only meet this on a folder that came from somewhere else.
With no project open at all, the panel says what source control is for and offers Clone Git Repository where the platform supports it.
Review your changes
The Local Changes tab lists every changed file, grouped by the part of the project it belongs to. Each row shows the file's name and a status badge: M for modified, A for added, U for a brand-new untracked file.
Click a changed file to see what changed since your last commit: the pane switches to its Diff editor, at full pane size. Put it in a second pane with [⌘] and the review sits beside the page it is about, both live.
Click + on a row to stage it (mark it for the next commit), or the header's stage-all button to stage everything. Staged files move to a Staged Changes section, where − unstages them, and an unstage-all button beside its count clears the section.
Click the undo icon on a row to discard its changes. Studio asks for confirmation first. An untracked file has nothing to go back to, so its undo icon is disabled rather than offering to throw the file away.
Discard permanently throws away a file's changes since the last commit. There is no undo beyond the confirmation dialog.
Commit and sync
Type a summary of your work in the message box.
Click Commit and sync . Studio records the commit and pushes it to your repository in one step. That push is what triggers your host's build, as described in Publish .
To record a commit without pushing, open the dropdown beside the button and choose Commit (don't sync) , or press ⌘Enter / Ctrl+Enter in the message box. If nothing is staged, the commit takes all changed files. Either way, Studio folds any live co-editing session into the files first, so a commit never misses the last few keystrokes a collaborator typed.
Stay in sync
The bar at the top of the panel shows where you stand against the repository, with a last-updated time: Up to date , or how many commits you are ahead or behind. Studio refreshes this automatically while the panel is open, and the circular arrow at the left of the bar re-checks on demand. Three buttons act on it:
Fetch : check the repository for news without changing your files.
Pull : bring teammates' commits into your copy.
Push : send your local commits up.
Studio also pulls automatically when you open a project that has a remote, so a session starts from the current state. If a pull can't merge cleanly, Studio reports the error and changes nothing. There is one exception: conflicts caused purely by Studio's own automated package updates are resolved for you (Studio discards its own machine-generated edits, pulls, and re-applies them; if you edited those files it asks before discarding anything).
A project with no remote yet shows Local only (no remote) here, with a Create GitHub repository shortcut.
Branches
The Active branch row shows which branch you're on. Use its picker to switch to another branch, or choose + New branch… . Studio opens a New Branch dialog; type a name and click Create . Branches let you try a redesign on the side and only merge it when it's ready.
History
The History tab lists your project's recent commits (short hash, message, author, and how long ago), so you can see how the site got to where it is. Before your first commit it explains what one is; with nothing changed since the last commit, Local Changes says so too.
Without the panel
Four of these verbs are also commands, listed in Quick Access under Source Control :
| Command | What it does |
|---|---|
| Initialize Repository | starts tracking the open project with git |
| Create GitHub Repository | creates a repository, sets it as the remote, and pushes |
| Push | sends the current branch to its remote |
| Sign In to GitHub | authorizes this machine, with or without a project open |
Naming them gives everything else something to point at: the deploy checklist puts them on its steps, a failed push can put Push itself on the Problem as a working button, and the AI assistant can run them. Initialize Repository is offered only where it makes sense (on a project git isn't already tracking), and says so when it isn't.
Sign In to GitHub belongs to the app rather than the project: a GitHub token is one per machine, and it's revoked in Preferences › Accounts . The other three belong to one repository.
Suite