Add-ons  /  Version control
Add-on

Know which folder is a repo.

A folder of checkouts looks the same in every file manager: twelve folders, no idea which one you left half-finished. Here the row tells you — repo, branch, and whether anything is uncommitted — and you can stage and commit without opening anything else.

Ships — you switch it on

What you do with it

On a normal Tuesday

01

See the state on the row.

Repositories are detected and each row carries its status, so “which of these has uncommitted work” is a glance, not twelve git status runs.

02

Stage and commit from the file list.

Right-click a changed file, stage it, write the message, commit.

03

Bind a credential to a remote.

The remotes page lists what the repository points at, and whether each one has a credential attached. Attach or clear it there.

Which bundles include it

How you come by it

An add-on is not sold on its own — a bundle is, and holding the same add-on through two bundles is never charged twice. See the bundles.

Ships, you switch it on

In the app, off until you move the slider

A fresh install hides anything below the default bar on this add-on’s Minimum readiness slider in Settings › Features. These are in the app today.

  • All of it. Every git feature is registered InTesting or Experimental, below the default bar, so a fresh install shows no git decorations until you move the Version control Minimum readiness slider in Settings › Features.
  • Merge-conflict surfacing.
Coming soon

Written, not yet reachable

Fetch, pull and push, and switching or creating a branch: the engine is written and the buttons are not wired to anything you can click yet. The diff in the preview pane is the same story (#6956), and so is the plain-English mode — you can choose it in Settings, but nothing you can open speaks it yet. What is here needs finishing and promoting, not replacing.

Version control is part of the file manager.

Download File Manager, then pick the bundle that grants it.