Git Review

When a connected folder is a Git repository, Undra gives it a review surface: the project’s history as a graph, the changes behind any commit as a readable diff, and a place to commit your work without leaving the app.

It is built for the part of Git you do while you are still thinking: seeing what changed, writing it down, looking back at how something used to be, and undoing a step that went wrong. It is deliberately local, and it never talks to a remote.

Open it

A connected folder that tracks its history shows a small Git badge with its branch name and, when there is uncommitted work, a count of changed files. Open the review from any of three places:

• The folder in the sidebar: click its Git badge.
• The Portals view: click the badge on the folder’s card.
• A running preview: use the controls in the preview bar.

The right-click menu on the folder also carries Review Git changes.

What you are looking at

The review opens as its own tab with two halves.

The history lists every commit as a single row, newest first, drawn on a graph where each branch gets its own column and its own color. The commit you have checked out is drawn as a filled node so you can find your place. If your project has uncommitted work, it sits at the very top on its own row, where your next commit will land.

The details pane shows whatever you select: for a commit, its message, author, and every file it touched; for your uncommitted work, the files you have changed. Selecting a file shows the diff with syntax highlighting, added and removed lines marked in the usual way. Very large diffs and binary files say so rather than trying to render.

You can search the history, and page back through it when a project has more commits than one screen holds.

Commit your work

From the row at the top of the graph:

1. Choose what goes in. Every changed file is listed with its status. Include all of them, or pick the ones that belong together.
2. Write the message. The field grows as you type.
3. Commit.

Undra commits only the files you reviewed, and only in that folder.

Look at an earlier version

Right-click any commit and choose View this version to put the project back the way it was at that point. This is not a preview of one file: the working folder really is checked out at that commit, so anything reading those files sees the older version.

Open previews reload themselves to match, which is the point. You can run the project as it was three weeks ago and click around it.

The preview bar shows you are looking at history rather than the present, and Back to latest returns you to your branch.

Branches

The review header shows the branch you are on and lets you switch to another one. Undra lists only local branches, so switching can never invent a branch or reach for a remote.

Uncommitted work comes with you across a switch, the way it normally does. When a file you have edited differs on the branch you are moving to, the switch stops and tells you to commit first, rather than overwriting anything.

Right-click any commit and choose Create branch here… to start a new branch at that point in history.

Undo a step

All of these live on a commit’s right-click menu, or on the file rows for uncommitted work. Each one checks the state of the folder first and refuses cleanly rather than leaving it half-changed.

• Discard changes throws away uncommitted edits to a file or to everything. A safety copy is kept inside the repository first, so a discard is recoverable for a while.
• Revert this commit adds a new commit that undoes an old one, leaving the history intact. This is the safe choice on work you have already shared.
• Drop this commit removes one commit and keeps everything after it. The commits that follow are rebuilt, so they get new identities.
• Roll back to this commit… drops everything after the commit you picked. The dropped commits stay recoverable through Git’s own reflog.
• Edit commit message rewords a commit. Rewording anything other than the most recent one rebuilds the commits after it, the same as dropping.

Merge commits are refused by the operations that would need to replay them, and anything that fails partway is rolled back to where it started.

What it deliberately does not do

This is a review and local-commit surface, not a full Git client:

• No push, pull, or fetch. Nothing here talks to a remote, and nothing here uploads your work. Use your terminal or your Git tool for that.
• No staging area to manage. You pick files at commit time instead of maintaining an index.
• No merges, no conflict resolution, no tags.
• One folder at a time. The review is scoped to the connected folder you opened it from.

Good to know

• Git has to be installed and on your system path. Undra runs your real git, so your existing configuration, hooks, and identity all apply.
• The history shows the most recent commits and pages back on demand rather than loading years of history at once.
• Undra’s own backups never enter your repository. Pre-edit backups taken when Mira changes files live in Undra’s app data, so they never appear in git status.
• The badge tracks the folder, so a change made outside Undra shows up here too.

Where to go next

• Folder Portals: connecting a real folder in the first place.
• Mira: the assistant that can make the changes you are reviewing.
• Local-First Trust: why Undra works on your real files.