Comments on: git how to: ignoring files in git

By: Tobias Schmidt

Tobias Schmidt — Sun, 12 Jul 2009 17:33:13 +0000

If you want to ignore further changes on a file without changing your repository use this command:

git update-index –assume-unchanged

By: Sharad Jain

Sharad Jain — Tue, 28 Apr 2009 16:53:02 +0000

http://GitReady.com/ is a great resource: Thanks for stopping by and pointing out.

By: greb

greb — Sun, 26 Apr 2009 06:35:38 +0000

You’ll need to do git rm –cached to keep the file in your tree and then ignore it.
From Here : http://www.gitready.com/beginner/2009/01/19/ignoring-files.html

By: Erik Petersen

Erik Petersen — Sat, 10 Jan 2009 15:55:37 +0000

You solve it by not having production configs in the repository and having Capistrano or whatever deployment system/script you use symlink database.yml to an immutable copy on the server.

That is the convention at least.

Thanks for your article. Git rocks and so does github.

By: Neil

Neil — Sat, 10 Jan 2009 08:36:47 +0000

Thanks for this round-up; I only knew about the first two options.

Has anyone found .gitignore to be intermittent? I often find I need to remove a file from the repo, delete the entry in .gitignore, return the file to the repo, then add the entry back in to .gitignore – otherwise it just won’t include the file in the list of ignored files. Is this just me or has anyone else seen this?

By: Antares Trader

Antares Trader — Sat, 10 Jan 2009 02:06:04 +0000

I feel you pain. I’ve forked a number of libraries where compiled binaries have snuck into the repository. (Bundled Merb apps prior to 1.06 like merb-book are the worst offenders.) The developer who owns these file has no reason to remove them they don’t bother him, but I clobber them every time I redeploy. I then have to meticulously keep them out of my commits because binary changes almost always create merge conflicts. If you find a solution let me know!