Git
Stage, unstage, and commit
Git · 2 min read
Pick which of your changes to keep as a set, write a note about them, and save that set into your project's history.
When you would want it
This is the point of source control: your work gets saved in labelled steps you can go back to, rather than as one big pile of edits.
Where to find it
- All Features → Stage, unstage, and commit
- Commit
- Stage all
- Unstage all
- Push
- Pull
- Fetch
- Initialise a repository
- Clone a repository
- Open Source Control
- Turn on or off
- Settings
What you get out of it
- History becomes readable steps instead of one pile of edits.
- Partial commits let you split unrelated changes apart honestly.
- Gutter marks in the editor keep showing what is still uncommitted while you work.
How to use it, step by step
- First commit on this machine? Open the terminal and tell git who you are once - git config --global user.name "Your Name" and git config --global user.email "you@example.com" - then come back and commit as normal.
- Open Changes in the Vibe sidebar for the Cursor-style view: an uncommitted +added −removed total, one row per file with its count, and the diff one click away.
- Untick a file to leave it out of this commit - until you do, every file is included.
- Press Commit & Push once: Agentfly commits the included files and pushes them, writing the message from the files if you leave it empty, and reports the result under the bar.
- Prefer the full panel? Open Source Control from the activity bar for the same list with side-by-side diffs, staging, and a separate push.
- The set enters your project's history as one labelled step you can return to, and the push result is reported in the same place.
Why this beats the usual way
Everything here drives real git on your machine - no proprietary VCS, no lock-in, no account. If you leave for another editor tomorrow, the repository is exactly as standard as it was.
Find it in Universal Search
Stage, unstage, and commit · Git