Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.gitignore Isn't the only way to ignore files in Git

nelson.cloud

Post reply on HN
Print view View original

21–30 of 188 posts

Re: .gitignore Isn't the only way to ignore files in Git

#21

Post by wpollock »

One point of clarification: with git, "global" means per-user, not "machine-wide. (I never understood why "--global" wasn't better named, maybe "--user".) That's why these pathnames are in a user's home (the "~" means the current user's home directory).

Machine-wide configuration is called "system" in git, and generally lives under "/etc".

Re: .gitignore Isn't the only way to ignore files in Git

#24

Post by digikata »

bryancoxwell wrote: post #4

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.

For quite a while, I've have had a shell fcn that will take all the untracked files listed in a git status, and push them to .git/info/exclude. Generally applied after an add+commit of everything I do want to go generally into the repo.

Re: .gitignore Isn't the only way to ignore files in Git

#26

Post by zahlman »

williamjackson wrote: post #13
judofyr wrote: post #12

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.

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

I have a new-repository script that creates a .local directory and puts a .gitignore with just `*` in it.

Re: .gitignore Isn't the only way to ignore files in Git

#27

Post by kevincox »

The global/user wide exclude is a feature that should be more widely known. I frequently have people submitting changes to add their IDE/OS/AI/... files to every project's .gitignore. They are almost always pleasantly surprised when I tell them that they can add them to their standard configuration and have them ignored everywhere without bothering every project and without risk of accidentally committing them on a project where they haven't updated the .gitignore yet.

My general rule is that in-repo .gitignore should only be used for repo-specific things (build outputs, dependency folders, ...) and most user tools should be in their own user config.

Re: .gitignore Isn't the only way to ignore files in Git

#28

Post by wccrawford »

kevincox wrote: post #27

The global/user wide exclude is a feature that should be more widely known. I frequently have people submitting changes to add their IDE/OS/AI/... files to every project's .gitignore. They are almost always pleasantly surprised when I tell them that they can add them to their standard configuration and have them ignored everywhere without bothering every project and without risk of accidentally committing them on a p…

I've always added it to the project's gitignore because I want to make sure nobody else adds those to the project, either, out of ignorance. I'm mainly doing it out of kindness to them, because I am definitely removing them from git again and it's going to cause them some pain.

In the future, I think I might just be less nice about it. I dunno.

Re: .gitignore Isn't the only way to ignore files in Git

#29

Post by weinzierl »

judofyr wrote: post #12

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.

Mine is

    aux
and I hide it by putting a .gitignore in it that just contains am asterisk (*), nothing else, that way it ignores itself and anything in it.

Re: .gitignore Isn't the only way to ignore files in Git

#30

Post by rafram »

onraglanroad wrote: post #20
rafram wrote: post #10

Earlier quoted context omitted.

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?!

Well, since I know what a delta is, and I know what an object is, I understand all of it.

Congratulations!
Post reply on HN