Skip to content
Browse files

Clean up .gitignore

Remove all the ignores from `.gitignore`. The default boilerplate
doesn't generate any project-specific files that need to be ignored. All
OS and Editor-generated files should be globally ignored rather than
polluting the local project ignores.

Further information on using git ignore's appropriately can be found in
the miscellaneous part of the bundled docs.
  • Loading branch information...
1 parent 703d0b8 commit 3ce6e98cde37308ce1207ad09970c54a266d0a9a @necolas necolas committed Aug 5, 2012
Showing with 2 additions and 52 deletions.
  1. +2 −52 .gitignore
54 .gitignore
@@ -1,52 +1,2 @@
-# Read about how to use .gitignore:
-# Numerous always-ignore extensions
-# OS or Editor folders
-# Dreamweaver added files
-# Komodo
-# Espresso
-# Rubinius
-# Folders to ignore
-# build script local files
+# Include your project-specific ignores in this file
+# Read about how to use .gitignore:

9 comments on commit 3ce6e98


Pretty'd be nice to have the right list. The link referenced misses a lot of the previous ignores (like sublime files, etc.). Also, probably a good idea to include /build/... stuff, since that is project specific.

H5BP member
necolas commented on 3ce6e98 Aug 6, 2012

There's a comprehensive set of ignores (include OS/Editor) linked to in the docs - - and also mentioned in the links at the bottom of that url. Since this project is now independent from the build script projects, so there's nothing here that needs to be ignored by default.


Gotcha & thx.


@necolas I like the change, but I think we can do a better page than github with giving a better 'recommended' set of ignores that mostly derives from the previous .gitignore here.

But then it's natural to wonder:
Why aren't github help pages open source, I can't contribute to them!
@defunkt help us help github!

Global gitignore FTW


A little late to this party, but I actually miss the old .gitignore file. While I understand the logic behind removing it, and the global ignore recommendation, it does has a hole.

The problem isn't with my own system (I'm using a global), or even my coworkers systems (who are also using globals). The problem occurs when bringing in outside developers who maybe don't have such a global ignore file set. By having an application specific file, I'm able to better ensure that these files don't get included in my repo.

Anyone have any advice on how to avoid this problem?


I'm probably not understanding the issue with outside developers, but from what I'm thinking I understand, why not make the .gitignore file part of the application by default in your initial commit for a new project, or git commit it if it's not already part of the application? This way new members to the team will get it when they clone the repo, and any changes to it that are application-specific will be shared by the team.

Any new application I build always begins with this one, which is derived from the original boilerplate:

The setup instructions I share with new members:

H5BP member

Anyone have any advice on how to avoid this problem?

Get them to use a global ignore. When you bring in outside developers, you must have a setup process to ensure they have all the correct dependencies and access to various systems. Part of that process should involve ensuring they are correctly ignoring files that shouldn't be under source control.


@necolas Gotcha, but things get ugly when people have different views on what files should be hidden globally.

H5BP member

@reinink you're still free to (mis)use the local .gitignore, which should contain project specific ignores.

Please sign in to comment.
Something went wrong with that request. Please try again.