A Collection of Useful .gitignore Templates

by gintas • 16 years ago

171 16 16 years ago

chr152• 16 years ago

If you are using Django/Python, it might be useful to add *.pyc to your gitignore. These are compiled python files.

Also, if you're developing on a Mac, it would also be useful to add .DS_Store. It's an invisible file, and it just stores some properties of that directory,

__mt0d• 16 years ago

I believe these are already covered:

  https://github.com/github/gitignore/blob/master/Python.gitignore

  https://github.com/github/gitignore/blob/master/Global/OSX.gitignore

chr152• 16 years ago

Yeah, I only looked at the Django gitignore.

mcav• 16 years ago

Anyone got a good Clojure one?

sirn• 16 years ago

The one created by Leiningen is pretty good.

    .cake
    pom.xml
    *.jar
    *.war
    lib
    classes
    build

xenomachina3• 16 years ago

It's interesting that the Java one doesn't list *.jar.

eeperson• 16 years ago

It seems like a lot of these should have leading slashes so they only match the root directory and not any file with that name.

avar• 16 years ago

Some projects like Git itself refuse to add editor droppings like ~ and # to .gitignore. They consider the .gitignore file to be only for things that the build system produces, e.g. *.o and binaries.

If you want to ignore things that your editor adds you should add it in .git/info/excludes, not .gitignore.

graywh• 16 years ago

I put text editor stuff in my global .gitignore

xenomachina3• 16 years ago

I think this is why the linked collection has all of the editor specific rules in a separate "Global" subdirectory.

pilif• 16 years ago

I'm of the opinion that artifacts of IDEs an OSes should not be part of a projects .gitignore. After all, different people could be using different environments for development and I really don't see the need for a projects .gitignore to contain the subset of all possible artifacts.

Use .git/info/exclude or a repository independent personal .gitignore for this.

The projects file is for files created by running the code or maybe some unavoidable build artifacts happening in all cases (.o files for example)

I really hate commits with messages like "updating .gitignore for Joe's new IDE"

A Collection of Useful .gitignore Templates

Related Stories