> For the complete documentation index, see [llms.txt](https://studio-docs.sandbox.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio-docs.sandbox.game/source-control/recommended-git-tools-git-bash-and-fork.md).

# Recommended Git tools Git Bash and Fork

Use this process when you want a simple Git tool setup for Sandbox Studio projects. Git Bash gives you a reliable command line, and Fork gives you a visual way to review changes, branches, and history.

## Step 1: Use Git Bash for commands

Open Git Bash when you need to run Git commands directly.

1. Open Git Bash from the Start menu.
2. Navigate to your project folder.
3. Run git status to confirm you are in the correct repository.

git status

The terminal shows the current branch and working tree state.

{% hint style="info" %}
*TIP: Use Git Bash when a tutorial gives a command to copy, when you need exact output, or when a visual tool does not show enough detail.*
{% endhint %}

## Step 2: Use Fork for visual review

Open Fork when you want to see changed files, branch history, and diffs visually.

1. Install Fork from <https://fork.dev> if it is not installed.
2. Open Fork.
3. Choose File, then Open Repository, and select your Sandbox Studio project folder.

![](https://content.gitbook.com/content/WgFjStdWWXj1Wc6xnrcJ/blobs/VxMeA6azPTrvXqJVaWme/Unknown%20image)

Fork shows the project repository, changed files, and recent history.

## Step 3: Review changes in Fork

Use Fork to inspect files before saving a checkpoint.

1. Open the Local Changes view.
2. Select each changed file and read the diff.
3. Confirm every changed file belongs to the current task.

The Local Changes view shows what will be saved if you commit the selected work.

{% hint style="warning" %}
*WARNING: Do not save generated files, secrets, credentials, or unrelated edits unless you understand why they belong in the project history.*
{% endhint %}

## Step 4: Use Git Bash for exact checks

Use Git Bash when you need a direct answer from Git.

1. Run git status to check current changes.
2. Run git remote -v to check the connected remote repository.
3. Run git branch to check the current branch.

git status

git remote -v

git branch

{% hint style="info" %}
*TIP: If Fork and Git Bash seem to disagree, refresh Fork and run git status again from the project root.*
{% endhint %}

## Step 5: Use Fork for branch history

Use Fork when you need to understand recent project history.

1. Open the repository in Fork.
2. Look at the commit graph to see recent checkpoints and branches.
3. Select a checkpoint to review the files changed by that work.

The commit graph shows how project work has moved over time.

## Step 6: Use the quick reference

Choose the tool based on the task you are doing.

| Task                            | Recommended tool |
| ------------------------------- | ---------------- |
| Run an exact command            | Git Bash         |
| Check current status            | Git Bash or Fork |
| Review file diffs               | Fork             |
| Understand branch history       | Fork             |
| Follow a command-based tutorial | Git Bash         |
| Choose files for a checkpoint   | Fork             |

## Step 7: Keep both tools available

Use Git Bash and Fork together instead of treating one as the only correct tool.

1. Use Git Bash when you need precise command output.
2. Use Fork when you need to review changes visually.
3. Check the result in both tools when something looks confusing.

## What You've Done

You have set up a practical Git tool workflow: Git Bash for commands and exact checks, Fork for visual review and history. Use both tools together to make [daily Git work](/source-control/daily-git-workflow.md) easier to understand and safer to review. For opening a repository in Fork, see [How to use Fork](/best-practices/how-to-use-fork.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://studio-docs.sandbox.game/source-control/recommended-git-tools-git-bash-and-fork.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.