Review, stage and commit changes

App version: 1.0.1iPad · iPhoneContent checked: 2026-09-21Screenshot UI: EnglishPro

What you will do

Save a reviewed change in your repository’s local history.

Before you start

• An active Pro subscription. Third-party AI subscriptions and API credits are separate.
• An existing Git repository. Use the separate tutorial repository for practice.

Download the tutorial workspace

Where to start

File browser → Files → Source Control

Follow the steps

1. 1Review the changed fileEdit and save hello.py, then open Source Control. Tap the changed file to read its diff.
2. 2Stage only the intended changesSwipe a change row to reveal Stage, or use Stage All after reviewing every file. Unstage removes a file from the next commit without deleting the edit.
3. 3Describe the changeEnter a short message such as Explain the greeting example. The commit button needs a message and at least one staged file.
4. 4Commit and check HistoryTap Commit. Confirm the new message appears in History. This records local history; it has not yet sent the commit to GitHub.

· Enlarge screenshot

1

See the control up close

PreviousNext

Close

1. Review the changed file — Edit and save hello.py, then open Source Control. Tap the changed file to read its diff.

1

2. Stage only the intended changes — Swipe a change row to reveal Stage, or use Stage All after reviewing every file. Unstage removes a file from the next commit without deleting the edit.

2

3. Describe the change — Enter a short message such as Explain the greeting example. The commit button needs a message and at least one staged file.

3

4. Commit and check History — Tap Commit. Confirm the new message appears in History. This records local history; it has not yet sent the commit to GitHub.

4

Check the result

Tap Commit. Confirm the new message appears in History. This records local history; it has not yet sent the commit to GitHub.

If it does not work

• Commit records local history; Push sends commits to the remote. Check which operation failed.
• For rejected pushes, inspect the remote changes and your permissions. Do not use a force push as a routine fix.
• If changes conflict, keep a copy and review the affected files before discarding anything.

Next steps

• Pull and push repository changes
• Open a pull request and resolve sync problems

Contact support