Version Control Git

Overview

Setup and maintenance of robust Git workflows for Unity projects. Includes optimized .gitignore configuration, Git LFS (Large File Storage) for binary assets, and collaboration strategies.

When to Use

•Use at project setup
•Use when binary assets (Texture, Audio) exceed 100MB
•Use when collaborating with teams
•Use when setting up CI/CD
•Use for branching and merging strategies

Key Configurations

File	Purpose
.gitignore	Excludes temp/generated files (Library, Temp, Logs)
.gitattributes	Defines LFS tracking (DLL, PNG, WAV, FBX)
.gitmodules	Manages submodules (Plugins, AntiGravity)

Unity Git Best Practices

•✅ YAML Serialization: Unity Editor -> Edit -> Project Settings -> Editor -> Asset Serialization -> Force Text.
•✅ Visible Meta Files: Unity Editor -> Edit -> Project Settings -> Version Control -> Mode -> Visible Meta Files.
•✅ LFS: Always track binary files with LFS to keep repo size distinct from history size.

Architecture

code

┌─────────────────────────────────────────────────────────────┐
│                    GIT LFS WORKFLOW                         │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  LOCAL REPO               REMOTE REPO (GitHub/GitLab)       │
│  ┌──────────────┐        ┌──────────────┐                   │
│  │ Source (.cs) │───────▶│ Source (.cs) │ (History)         │
│  │ Meta Files   │        │ Meta Files   │                   │
│  │              │        └──────────────┘                   │
│  │ LFS Pointer  │───────────────┐                           │
│  └──────┬───────┘               │                           │
│         │                       ▼                           │
│         │                ┌──────────────┐                   │
│         └───────────────▶│ LFS STORAGE  │ (Binaries)        │
│    (Actual Binary)       │ .psd .fbx    │                   │
│                          └──────────────┘                   │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Few-Shot Examples

Example 1: Unity .gitignore

User: "Generate gitignore for Unity."

Agent:

gitignore

# Unity generated
/[Ll]ibrary/
/[Tt]emp/
/[Oo]bj/
/[Bb]uild/
/[Bb]uilds/
/[Ll]ogs/
/[Uu]ser[Ss]ettings/

# Visual Studio / Rider
.vs/
.idea/
*.csproj
*.sln
*.user
*.suo

# OS generated
.DS_Store
Thumbs.db

Example 2: .gitattributes (LFS)

User: "Setup LFS for textures and models."

Agent:

gitattributes

# Image formats
*.jpg filter=lfs diff=lfs merge=lfs -text
*.jpeg filter=lfs diff=lfs merge=lfs -text
*.png filter=lfs diff=lfs merge=lfs -text
*.psd filter=lfs diff=lfs merge=lfs -text
*.tga filter=lfs diff=lfs merge=lfs -text

# Audio formats
*.wav filter=lfs diff=lfs merge=lfs -text
*.mp3 filter=lfs diff=lfs merge=lfs -text
*.ogg filter=lfs diff=lfs merge=lfs -text

# 3D formats
*.fbx filter=lfs diff=lfs merge=lfs -text
*.obj filter=lfs diff=lfs merge=lfs -text
*.blend filter=lfs diff=lfs merge=lfs -text

# Unity binaries
*.unitypackage filter=lfs diff=lfs merge=lfs -text
*.dll filter=lfs diff=lfs merge=lfs -text

Example 3: Branching Strategy

User: "Explain GitFlow for our team."

Agent:

code

1. main: Production-ready code.
2. develop: Integration branch for features.
3. feature/feature-name: Individual developer work.
4. release/v1.0: Preparation for release (bug fixes only).
5. hotfix/critical-bug: Urgent fixes for main.

Rules:
- Never push to main/develop directly.
- Use Pull Requests (PRs) for code review.
- Squash commits when merging feature branches to keep history clean.

Related Skills

•@tools-pipeline - CI/CD setup
•@unity-mcp-connector - Editor integration