Skip to content
Browse files

begin! add Rails and Obj-C templates

  • Loading branch information...
0 parents commit b7cc33a99b02fada900d0e4ba6b7bd38a142f064 @defunkt defunkt committed Nov 8, 2010
Showing with 16 additions and 0 deletions.
  1. +8 −0 Objective-C.gitignore
  2. +3 −0 README.md
  3. +5 −0 Rails.gitignore
8 Objective-C.gitignore
@@ -0,0 +1,8 @@
+# xcode
+build/*
+*.pbxuser
+*.mode1v3
+*.perspectivev3
+# osx
+.DS_Store
@adamv
adamv added a note Nov 8, 2010

This really ought to be in a Mac OS dev's global ignores!

@defunkt
GitHub member
defunkt added a note Nov 8, 2010

Ah yes -- agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
+profile
@kylef
kylef added a note May 9, 2013

This is really broad, what file should it specifically ignore?

I've never seen any profile before. I got caught out by the .gitignore ignoring my "PLVProfileViewController".

@groue
groue added a note Nov 15, 2013

Same issue here. Which profile file/folder did you want to prevent ? It's important to answer, so that the ignored path gets more precise.

@plasmabal
plasmabal added a note Dec 23, 2013

CocoaPods uses Profile. Any files with "profile" (case-insensitive) in the name will be ignored, so why is it here? I had a .gitignore similar to this file and it works fine with profile removed.

@kylef
kylef added a note Dec 23, 2013

@plasmabal That's incorrect, I think you mean Podfile not profile.

@plasmabal
plasmabal added a note Dec 23, 2013

@kylef Ya, you're right. What was I thinking... Anyway, I was bitten by profile several times before so I removed it. And I don't remember I encountered any other files stop from working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 README.md
@@ -0,0 +1,3 @@
+# A Collection of Useful .gitignore Templates
+
+Thanks.
5 Rails.gitignore
@@ -0,0 +1,5 @@
+.bundle
+log/*
+tmp/*
+db/*.sqlite3
+public/system/*

0 comments on commit b7cc33a

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