Hacker News new | ask | show | jobs
by bmacho 1058 days ago
Why wouldn't it work? You gitignore that file, and your modification is ignored, even if it is committed? Or will git delete that file from everyone?
1 comments
Groxx 1058 days ago
gitignores are usually committed (they're treated like a normal file), so yes, in this context that would delete it from everyone.

There's .git/info/exclude, but that has some kinda large surprises if it excludes a tracked file and I don't recommend anyone use it unless they know what to look for and can always remember what they've excluded.

link
sanderjd 1058 days ago
I have a $HOME/.gitignore that I use for this. (You can configure git to use that globally.) It's not a panacea, and I think other commenters are right that you should instead endeavor to organize things so that the project's own gitignore results in a sane workflow. But I think having permanently unstaged changes is worse.
link
happymellon 1058 days ago
It's the perfect location to ignore *.log.

Git will fight you if you ignore .config files which are actually used.

link