Where should I place my global ‘gitattributes’ file?

by

Global vs. system-wide settings

There is some ambiguity in your question’s terminology.
In a Git context, “global” usually means “user-level”; in other words, a global setting affect all repositories for one specific user (the active one). In contrast, a system-wide setting affects all repositories for all users of a machine.

Repository-level gitattributes

(I’m only mentioning this for completeness.)

According to the relevant section of the Pro Git book,

If you wish to affect only a single repository (i.e., to assign attributes to files that are particular to one user’s workflow for that repository), then attributes should be placed in the $GIT_DIR/info/attributes file.

$GIT_DIR would typically expand to <path-to-repo-root-directory>/.git.

Global (user-level) gitattributes

According to the relevant section of the Pro Git book,

Attributes that should affect all repositories for a single user should be placed in a file specified by the core.attributesfile configuration option […]. Its default value is $XDG_CONFIG_HOME/git/attributes. If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/attributes is used instead.

You can also run the following command,

git config --global core.attributesfile <path>

to point Git to a custom path <path> for your global gitattributes file, e.g. ~/.gitattributes.

System-wide gitattributes

According to the relevant section of the Pro Git book,

Attributes for all users on a system should be placed in the $(prefix)/etc/gitattributes file.

which naturally begs the question:

[…] But where is $(prefix)?

See What is $(prefix) on $(prefix)/etc/gitconfig? for an answer. Unless you’ve assigned prefix a custom, non-empty value, $(prefix) expands to nothing by default; therefore, your system-wide gitattributes file should reside in /etc/.

More Related Contents:

  1. git smudge/clean filter between branches
  2. git-upload-pack: command not found, when cloning remote Git repo
  3. How can I make git ignore future revisions to a file?
  4. How do I get bash completion to work with aliases?
  5. How to normalize working tree line endings in Git?
  6. git difference on parameter one dash and two dashes
  7. Force “git status” to output color on the terminal (inside a script)
  8. git command for making one branch like another
  9. GitHub folders have a white arrow on them
  10. What’s the difference between HEAD, working tree and index, in Git?
  11. How to remove selected commit log entries from a Git repository while keeping their changes?
  12. Git: “Corrupt loose object”
  13. How to read the output from git diff?
  14. How to use git bisect?
  15. How do I tell Git to ignore everything except a subdirectory?
  16. Using Git, show all commits that are in one branch, but not the other(s)
  17. How to get the changes on a branch in Git
  18. Git branching: master vs. origin/master vs. remotes/origin/master
  19. Creating SSH keys for Gerrit and Hudson
  20. How does git commit –amend work, exactly?
  21. Detach many subdirectories into a new, separate Git repository
  22. Git push results in fatal: protocol error: bad line length character: This
  23. Git – finding the SHA1 of an individual file in the index
  24. Is there a way with to prevent “git stash pop” from marking files as modified?
  25. Visual Studio Code is always asking for Git credentials
  26. How do negated patterns work in .gitignore?
  27. Git: How to reset a remote Git repository to remove all commits?
  28. Renaming a branch in GitHub
  29. Git: Merge a Remote branch locally
  30. Using two git repos in one folder

Leave a Comment