Select changes and create a commit
Select the intended files and save a local Git commit.
Last updated 16 September 2026
Select the intended files and save a local Git commit.
Before you start
Review the changes and complete the relevant checks first. Confirm whether Git is showing the main project or a Solo workspace.
The demo Solo contains one staged file and a reviewed message. Committing records these selected changes locally.
Step by step
Open Git → Changes and inspect each file’s diff. Look for unrelated edits, generated files, and private configuration before staging.
Use a file’s checkbox or Stage control to include it. Use Stage All only when every listed change belongs in this commit.
Check the Staged section. Untracked files must be deliberately included; selecting a conversation does not make every repository change part of that task.
Enter a concise commit message describing the result. If you use Generate, review the generated wording before committing.
Choose Commit and wait for the result. Resolve any reported hook, identity, or repository error before retrying.
Open Git → Commits and confirm the new message and commit are present. Return to Changes to inspect anything left uncommitted.
What to expect
The selected changes are recorded locally, with unrelated files left out of that commit.
Troubleshooting and useful details
The screenshot shows one staged Markdown file in a demo Solo branch. The example was committed locally and appeared in Commits. A local commit does not push code or create a pull request; those are separate actions.