-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reworked .gitignore #20
Conversation
… folder now empty with just a dedicated .gitignore file
+1, merge away. |
I think it is a better approach to keep the ignoring rule for the var folder in the global This is the approach I have used to handle git disability to track empty directories.
Having this in place and whenever I need to track a directory, all I need to do is this |
I agree it's cleaner to just have a single .gitignore file. Pull request adjusted. |
As discussed just now, the addition of the extension and settings rules seems catered to committing back to this repo only. We need to consider how this will get used on actual client projects. |
I now changed it. The new version is a better fit for client projects: only ignoring everything in the var folder. To keep the var folder it now contains a '.gitkeep' file. |
@pkamps the .gitignore is missing the .gitkeep exclusion rule that Ernesto mentioned no? |
You're right - I updated .gitignore now |
+1 |
Reworked .gitignore to ignore additional extensions and settings - var folder now empty with just a dedicated .gitignore file.
It would allow you to clone the project and add client specific extensions, settings and assets (in the var dir) without having those showing up as new files.