Py Editor MAC USER MANUALDeveloper ID · 27.0.2 (32)
REVIEWED EDITION · Developer ID 27.0.2 (32)

Track local changes with Git

Py Editor can create and use a Git repository without publishing anything. This chapter covers a verified local workflow: initialize a repository, choose files, commit, read history, create a branch and return to main.

The review used a disposable two-file project in Developer ID 27.0.2 (32). It had no remote, no account operation and no push. Use a copy of important work while learning these controls.

Start a local repository

  1. Open the project folder in Py Editor.
  2. Open Commit in the left tool rail.
  3. If the panel says Not a Git repository, choose Start a local repository. The branch control in the top toolbar offers the same action as Create Local Git Repository….
  4. Confirm that the toolbar now shows main and that new files are marked Untracked.

In the reviewed project, initialization created the local .git directory and did not create a remote. The editor immediately marked README.md and main.py as untracked. Creating a repository does not publish the folder.

Inspect a working-tree change before committing

  1. Save a small change in the disposable project.
  2. Open Commit and choose Refresh if the panel still says Working tree clean.
  3. Select the changed filename, not its inclusion checkbox.
  4. Read Working Tree Diff. The left side is HEAD and the right side is Working Tree; the header reports removed and added line counts.
  5. Choose Close diff and return to the editor when you finish comparing.

The reviewed README change added two lines. The header showed −0 +2, and the right side displayed the temporary sentence while the left side stopped at the committed text. Opening the comparison also opened README.md in an editor tab; it did not select the file for commit or create a commit. The temporary sentence was removed afterward, Refresh returned the panel to Working tree clean, and Reload From Disk restored the original editor text. Use the inclusion checkbox only after you have decided that the complete file belongs in the next commit.

Choose files and create the first commit

  1. Open Commit.
  2. Review the changed-file list. Select files individually, or use Include all changed files only after reading the full list.
  3. Enter a short commit message that describes the saved state.
  4. Choose Commit. Do not choose Push for a local-only repository.
  5. Wait for Working tree clean.

The reviewed commit included exactly the two fixture files. After committing, the panel showed Working tree clean. This verifies the app's local selection and commit path; it does not verify signing, a remote host or collaboration.

Read commit history

  1. Open Git log in the Bottom area, or choose Git → Git Log.
  2. Select a commit to inspect its recorded changes.
  3. Use Refresh history after another Git operation if the list is stale.

The local commit appeared immediately with its message and short identifier. History is evidence of a commit only in this repository; it is not evidence that the work exists on GitHub or another server.

Create a branch and return to main

  1. Open the branch menu in the top toolbar.
  2. Choose New Branch….
  3. Enter a descriptive branch name. The review used manual-review.
  4. Choose Create. The toolbar changes to the new branch.
  5. Open the branch menu again, choose Switch Branch, then choose main.
  6. Confirm that the toolbar says main and the Commit panel still says Working tree clean.

This procedure creates and switches a local branch. It does not merge it or delete it. Keep the branch if you still need its work; deletion and conflict recovery are not covered by this tutorial.

Know when a remote is required

The Git menu also contains Fetch, Pull, Pull with Rebase and Push…. Those commands communicate with a configured remote and can change local or remote history. The reviewed fixture intentionally had no remote: Copy Repository URL was unavailable, and no network Git operation was run.

Before using a remote command, check the repository URL, the active branch and the files or commits involved. A successful local commit does not authorize a push. Account sign-in, remote setup, pull/rebase, merge, conflict resolution, amend, discard and branch deletion remain outside this verified workflow.