Stage, unstage, and commit
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
- Settings → adcode.git.stageCommitUi
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
- Open the Source Control panel from the activity bar.
- Review the changed files; click any one to see its diff side by side.
- Tick the changes that belong together - that is staging.
- Write a short message saying what this set does.
- Press Commit. The set enters your project's history as one labelled step you can return to.
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