Pull and push repository changes

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

What you will do

Bring remote commits into a working copy and send your own commits back.

Before you start

• An active Pro subscription. Third-party AI subscriptions and API credits are separate.
• A working internet connection for the service or download used in this tutorial.
• An existing Git repository. Use the separate tutorial repository for practice.

Download the tutorial workspace

Where to start

Source Control → Pull / Push

Follow the steps

1. 1Check the repository and accountConfirm the project has an origin remote and that your GitHub account can access it. A new local repository needs a remote configured before it can sync.
2. 2Pull before continuing workSave and review your current changes, then tap Pull. Read any rejection before making further edits.
3. 3Push completed commitsAfter committing locally, tap Push. Uploading saved files without a commit is not the same operation.
4. 4Verify on GitHubOpen the matching branch on GitHub and check the new commit message and file content. For remote workspaces, Git runs on the server and uses that server’s Git credentials.

· Enlarge screenshot

1

See the control up close

PreviousNext

Close

1. Check the repository and account — Confirm the project has an origin remote and that your GitHub account can access it. A new local repository needs a remote configured before it can sync.

1

2. Pull before continuing work — Save and review your current changes, then tap Pull. Read any rejection before making further edits.

2

3. Push completed commits — After committing locally, tap Push. Uploading saved files without a commit is not the same operation.

3

4. Verify on GitHub — Open the matching branch on GitHub and check the new commit message and file content. For remote workspaces, Git runs on the server and uses that server’s Git credentials.

4

Check the result

Open the matching branch on GitHub and check the new commit message and file content. For remote workspaces, Git runs on the server and uses that server’s Git credentials.

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

• Open a pull request and resolve sync problems
• Manage remote files with SFTP

Contact support