.gitignore Isn't the Only Way to Ignore Files in Git

Y	Hacker News new \| ask \| show \| jobs

	.gitignore Isn't the Only Way to Ignore Files in Git (nelson.cloud)
	61 points by FergusArgyll 4 hours ago

4 comments

judofyr 8 minutes ago

Not sure where I picked up this, but I’ve added this to my global Git ignore:

    attic

That way you can just create an attic directory in any project where you can keep random stuff that should never be committed. I’ve yet to find a repo which actually has such a directory checker in.

link

williamjackson 4 minutes ago

I do this too! But I call it `.local`

link

Hendrikto 46 minutes ago

This is just a very low-effort regurgitation of this: https://git-scm.com/docs/gitignore

link

_the_inflator 25 minutes ago

You made my day. Everything is said and explained there.

Ok, sometimes a more vivid and visually explanatory style would help, but here still Google is your friend for individual concepts.

One of the best resources there is. git is a hell of a tool. It looks simple but is so beautifully versatile without being complex or not deductive.

link

y2244 17 minutes ago

"Google is your friend for individual concepts."

Asking aLlm is the new google

link

b40d-48b2-979e 11 minutes ago

    git is a hell of a tool. It looks simple but is so beautifully versatile without being complex

    without being complex

Uh, what?

link

rafram 10 minutes ago

What part of

   Enumerating objects: 15, done.
   Counting objects: 100% (15/15), done.
   Delta compression using up to 10 threads
   Compressing objects: 100% (8/8), done.
   Writing objects: 100% (8/8), 1.43 KiB | 1.43 MiB/s, done.
   Total 8 (delta 7), reused 0 (delta 0), pack-reused 0 (from 0)
   remote: Resolving deltas: 100% (7/7), completed with 7 local objects.

don't you understand?!

link

jagged-chisel 41 minutes ago

Hey, come on now - they added 'check-ignore' which is good complementary advice.

link

hk1337 12 minutes ago

~/.config/git/ignore and ~/.config/git/config is the proper place for your global git config and ignore instead of creating a ~/.gitignore_global and changing the config. IMO.

my dotfiles are a lot smaller at the root level taking advantage of the ~/.config/ for a lot more things.

the git exclude isn't used as much because it doesn't get committed to the repository so you'd have to recreate it each time you wanted to use it. that doesn't mean they're bad just why they are not used.

link

b40d-48b2-979e just now

As a bonus, you can (should?) version control your `~/.config` dir to enable future revisions and sharing.

link

bryancoxwell 35 minutes ago

I use the ever living hell out of .git/info/exclude. Works great for scripts/Makefiles I only want locally and collaborators wouldn’t care about or be able to use.

link

RSHEPP 12 minutes ago

Interested in examples of the types of scripts others collaborators wouldn't be able to use? Like scripts for PR workflows?

link

junon 8 minutes ago

Usually when I'm working in one part of the codebase and I have sample data or something at a specific path on my local machine and Im testing the same thing over and over again will I make a Makefile or something and info/exclude it to help me keep focused. That's one way I use it.

link