Hacker Read

rjmunro · 2023-03-28 03:49:09

Something like:

git config --global core.excludesfile ~/.gitignore-global echo .DS_Store >> ~/.gitignore-global

tracker1 | karma 11460 | avg karma 1.11 · | 2024-05-28 17:35:47

For what it's worth...

  echo ".DS_Store\n" >> ~/.gitignore
  git config --global core.excludesFile "~/.gitignore"

throwaway8941 | karma 908 | avg karma 4.2 · | 2020-02-27 11:29:01+00:00

Put them into your global .gitignore

    echo -e >>~/.config/git/config '[core]\n    excludesFile = ~/.config/git/gitignore'
    echo >>~/.config/git/gitignore '.env'

sjs | karma 3189 | avg karma 3.09 · | 2011-12-25 00:47:17

For git users:

    echo ".DS_Store" >> ~/.gitignore
    git config --global core.excludesfile ~/.gitignore

If you spend many man hours dealing w/ .DS_Store files in source code repos you're doing something wrong.

Dobbs | karma 2030 | avg karma 3.46 · | 2022-05-18 03:41:56

Additionally git supports a global git ignore.

    $ git config --global core.excludesfile ~/.gitignore

Then you can put all the standard things you want to ignore into it:

    $ cat ~/.gitignore
    .DS_Store
    ./drafts/
    *.swp

And it will apply to all git commands on your computer.

mikl | karma 3080 | avg karma 4.99 · | 2022-05-18 15:08:28

Or simply put the file at the default location for core.excludefile, which is

    ~/.config/git/ignore

on Unixy platforms.

bacon_waffle | karma 1216 | avg karma 2.63 · | 2020-06-26 04:24:25+00:00

git can be configured to ignore .DS_Store by default - in your home directory, make a .gitignore file using the usual format, then do "git config --global core.excludesfile ~/.gitignore".

pjot | karma 767 | avg karma 2.43 · | 2023-03-23 21:42:13

lgtm.

A global .gitignore is one of the first things I install on a new machine - and then I never think of it again.

  $ git config --global core.excludesfile ~/.gitignore

jacobparker | karma 1417 | avg karma 6.35 · | 2021-01-31 15:48:39+00:00

You might be interested in:

git config --global core.excludesfile ~/.gitignore

You can have a system-wide (but local only) .gitignore. It doesn't help other people who clone your repo, but it can be useful in some situations.

reply

maximilianroos | karma 2988 | avg karma 9.86 · | 2023-07-26 19:09:54

Great tip! Didn't know about this.

A similar one: ~/.config/git/ignore is a global private gitignore.

Great for files across repos which you always want to ignore, such as temporary files from an editor

reply

arp242 | karma 17029 | avg karma 3.74 · | 2023-08-01 07:01:21

> There should be a .local.gitignore to somesuch

I think .git/info/exclude is what you're looking for? (and also the global ~/.config/git/ignore)

reply

bdr | karma 9277 | avg karma 8.1 · | 2010-02-18 03:52:58

Yes, that's what I'm already doing. The question is what to put as your core.excludesfile setting in the .gitconfig file.

yrro | karma 2501 | avg karma 1.97 · | 2023-03-28 05:11:42

You don't need to set core.excludesfile any more, it defaults to ~/.config/git/ignore these days

zb | karma 1776 | avg karma 3.91 · | 2011-06-20 11:12:54

It's much better to ignore the files generated by your own tools with a global exclude file than to add them to every project's .gitignore.

  git config --global core.excludesfile ~/.gitignore

lilyball | karma 19000 | avg karma 20.99 · | 2020-06-26 04:50:52+00:00

Better still is to put it in ~/.config/git/ignore and leave your core.excludesFile unset, as that's the default path and will therefore live right next to your config file.

smcleod | karma 8476 | avg karma 6.43 · | 2023-01-23 06:50:08

Yeah I've been using that for quite some time and it's incredibly useful.

You can also set a global ignore file, which you could set in one of your path based includes.

  [core]
    excludesfile = ~/.gitignoreglobal

https://github.com/sammcj/zsh-bootstrap/blob/master/.gitconf...

jwilk | karma 8094 | avg karma 2.47 · | 2023-01-23 16:05:28

There's also .git/info/exclude:

> Patterns which should be version-controlled and distributed to other repositories via clone (i.e., files that all developers will want to ignore) should go into a .gitignore file.

> Patterns which are specific to a particular repository but which do not need to be shared with other related repositories (e.g., auxiliary files that live inside the repository but are specific to one user’s workflow) should go into the $GIT_DIR/info/exclude file.

> Patterns which a user wants Git to ignore in all situations (e.g., backup or temporary files generated by the user’s editor of choice) generally go into a file specified by core.excludesFile in the user’s ~/.gitconfig. Its default value is $XDG_CONFIG_HOME/git/ignore. If $XDG_CONFIG_HOME is either not set or empty, $HOME/.config/git/ignore is used instead.

https://git-scm.com/docs/gitignore

reply

thayne | karma 6329 | avg karma 2.83 · | 2022-05-18 18:40:51

That's cool!

You can also put local gitignore rules in .git/info/exclude , but i have a hard time remembering that exact path for some reason.

reply

Deradon | karma 61 | avg karma 3.05 · | 2022-05-18 04:36:38

Another comment already mentioned the `.git/info/exclude` directory. For completeness link to the online docs: https://git-scm.com/docs/gitignore

git will take 3 files into consideration for "ignoring" files:

> $XDG_CONFIG_HOME/git/ignore, $GIT_DIR/info/exclude, .gitignore

How I use them:

* ~/.gitignore: stuff I want to ignore everywhere (`/myNotes`, `.DS_STORE`, ...)

* <project>/.gitignore: stuff that should be ignore for this projects and shared with others

* <project>/.git/info/exclude; stuff for this project that only I want to ignore

** this is also super useful in combination with `git-bisect`

reply

charcircuit | karma 2002 | avg karma 0.38 · | 2023-03-27 22:10:50

By that logic it should be in your global excludes file. It practice it will save more time if you just add it to your project's .gitignore instead of wasting time having everyone else configure their system. O(1) amount of work compared to O(n)