Skip to content
Bit Quirky Round Trip
Visual Scripting

Search documentation

All topics and APIs

Close returns focus to Search.

What are you looking for?

Try a common topic or a C# feature.

Browse the reference instead

Esc closes · Tab reaches results · Enter opens the focused link

v1.0.0
Menu

Git

What Round Trip needs from a Git repository, how it shows your uncommitted changes, and where to learn Git properly if you do not use it yet.

Round Trip reads a Git repository to show which classes changed since your last commit; committing, diffing and restoring files stay in your own Git tool. If you do not use Git yet, Unity Version Control is the easier road for a Unity project; Choose your strategy compares them.

The free Pro Git book covers Git properly, and GitHub’s GitHub Desktop documentation covers the same work without a terminal. Install Git itself from git-scm.com; Round Trip runs the git program it finds on your computer, even when you commit from a graphical app.

Two things are specific to Unity, and both must be in place before the first commit:

  • A .gitignore that keeps Library, Temp, Logs, obj, UserSettings and build output out of the repository. Use GitHub’s Unity template as it is.
  • Git LFS for textures, audio, models and other large binary files, set up before those files are committed. GitHub’s Git Large File Storage section covers installing it, tracking file types and what to do when files were committed first.

For Round Trip itself: commit ProjectSettings/RoundTripSettings.asset, which holds the folders Round Trip reads, so the team indexes the same code. Commit the RoundTrip folder only when the team uses Shared layouts (Layout and configuration files). UserSettings stays out; it holds each person’s own layouts and last open method.

Commit before you edit, or before an AI assistant edits, and commit again afterwards. Your last commit is the version you can go back to in your Git tool, so frequent commits keep it useful.

Review saved source changes

Select a screenshot to enlarge it.

The actual Changes list contains a modified PlayerController and its changed-method count. The Changes button in the toolbar and the PlayerController row are highlighted, with an arrow pointing at the button.
Figure 1. Find the changed class This example uses a real Git-backed source edit. Open Changes to choose the class you need to inspect. Other uncommitted work can appear in the same list.
The actual RefreshHud method has an M marker and its saved diagram is visible.
Figure 2. Open the marked method The M identifies a source change since the baseline. Read that method’s behavior, then review or restore the whole file with your version-control tools when needed.

Use your Git tool. Restoring a file from HEAD or from an earlier commit, reverting a commit, and looking at a file’s history are ordinary Git operations, and the guides above cover them. Before any of them, keep pending work you still need: commit it, stash it, or copy the affected files aside.

The published repository is your off-machine copy. An occasional independent backup guards against losing the repository or the host account.

When it goes wrong

SymptomCheckFix
The Changes button is grayed out.Hover it. The tooltip reads No version control detected.Open the Unity project from inside the repository, with its .git folder present.
The Changes list is empty or the button is grayed out although you changed files.Run git --version in a terminal, and check that the project folder is inside the repository.Install Git if it is missing, or open the project from inside the repository, then reopen Unity.
Full-size image