> For the complete documentation index, see [llms.txt](https://gregorigin.gitbook.io/safesave/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gregorigin.gitbook.io/safesave/the-traffic-light/setup-git-and-lfs-5-mins.md).

# Setup Git & LFS (5 Mins)

**Stop emailing zip files.**\
This guide sets up a robust Git workflow with LFS (Large File Storage) support, which is mandatory for Unreal binary assets.

#### **Step 1: Install GitHub Desktop**

Download and install [GitHub Desktop](https://www.google.com/url?sa=E\&q=https%3A%2F%2Fdesktop.github.com%2F). It provides a visual interface for Git management.

#### **Step 2: Create the Repo**

1. In GitHub Desktop: **File > New Repository**.
2. **Name:** MyGame
3. **Local Path:** Choose a folder on your SSD.
4. **Git Ignore:** Select **UnrealEngine**. (Crucial step!)
5. Click **Create Repository**.

#### **Step 3: Enable LFS (Large File Storage)**

Unreal assets are binaries. Git needs LFS to handle them.

1. In GitHub Desktop: **Repository > Show in Explorer**.
2. Create a text file named .gitattributes.
3. Paste this configuration into it:

   code Text
4. ```
   *.uasset filter=lfs diff=lfs merge=lfs -text
   *.umap filter=lfs diff=lfs merge=lfs -text
   *.upk filter=lfs diff=lfs merge=lfs -text
   *.fbx filter=lfs diff=lfs merge=lfs -text
   *.png filter=lfs diff=lfs merge=lfs -text
     
   ```
5. Commit this file: "Setup LFS".
6. Click **Publish Repository**.

#### **Step 4: Connect Unreal**

1. Move your .uproject and Content folder into this new repository folder.
2. Open Unreal Engine.
3. **Source Control (Bottom Right)** -> **Connect**.
4. Select **Git (Beta)**.

**You are now ready to use SafeSave.**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gregorigin.gitbook.io/safesave/the-traffic-light/setup-git-and-lfs-5-mins.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.