.gitattributes Generator

A .gitattributes file is a Git configuration file placed in your repository root (or any subdirectory) that assigns attributes to file paths. These attributes control how Git handles line endings, diff output, merge strategies, export rules, and even how GitHub classifies languages via linguist attributes. It ensures consistent behavior across all contributors regardless of their operating system.

CRLF (\r\n) is the traditional Windows line ending — two characters: Carriage Return + Line Feed. LF (\n) is the Unix/Linux/Mac line ending — a single Line Feed character. When developers on different OSes work on the same files without proper Git configuration, you may see entire files marked as changed due to line ending differences. Setting * text=auto in .gitattributes tells Git to automatically normalize line endings to LF in the repository while checking out CRLF on Windows working trees.

* text=auto is the recommended best practice for most projects. It tells Git to automatically detect whether each file is text or binary. For text files, Git normalizes line endings to LF on commit, and checks out with the platform-appropriate ending (CRLF on Windows, LF on Unix). For binary files (images, archives, etc.), Git leaves them untouched. This single line prevents most cross-platform line ending issues.

Mark binary files with the binary attribute to tell Git they should not be diffed, merged, or have their line endings modified. For example: *.png binary, *.jpg binary, *.zip binary. You can also use -diff -merge -text as a more explicit equivalent. For Unity projects, files like .unity, .prefab, .asset, and .mat should be marked as binary.

Absolutely yes! The .gitattributes file should be committed to your repository so that every contributor uses the same settings. Git applies attributes from .gitattributes files found in the repository. If each developer had their own local configuration, you'd still face inconsistent line endings and diff behavior. Committing it ensures team-wide consistency and is a hallmark of a well-configured project.

Linguist is GitHub's language detection library. Linguist attributes in .gitattributes let you override its behavior: linguist-vendored marks third-party/vendor code (excluded from stats), linguist-generated marks auto-generated files, linguist-documentation marks documentation files, and linguist-language=Python forces a specific language classification. These are incredibly useful for cleaning up your repository's language statistics on GitHub.

The export-ignore attribute tells git archive to exclude matching files from generated archives (tarballs, zip files). This is handy for excluding development-only files like .github/ workflows, tests/, .editorconfig, or CI configs from release packages. Example: .github/* export-ignore or tests/* export-ignore. It keeps your release artifacts clean and professional.

Unity projects require special care: scene files (.unity), prefabs (.prefab), assets (.asset, .mat) are binary and should be marked binary. Meta files (.meta) should be text eol=lf. C# scripts (.cs) and shaders should use text eol=lf. Our Unity preset handles all of these automatically — just load it and you're set.

.gitignore tells Git which files to completely ignore — they won't be tracked at all. .gitattributes tells Git how to handle tracked files — line endings, diff behavior, merge strategies, etc. They serve different purposes but work together. A well-configured project typically has both: .gitignore for build artifacts and IDE files, .gitattributes for consistent file handling across platforms.

Yes! You can place .gitattributes files in subdirectories. Git applies attributes from the file closest to the matched path. A root .gitattributes provides project-wide defaults, while subdirectory .gitattributes files can override or extend rules for specific folders. Patterns in subdirectory files are relative to that directory. This is useful for monorepos or projects with distinct subsystems.