This repository has been archived by the owner on May 29, 2018. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
081c299There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like something that is best to have in your personal gitignore for this repo, rather than something that is applicable to the entire project as a whole (e.g., people who don't use Sublime won't benefit from this file).
See https://stackoverflow.com/a/1753104/622447 and
gitignore(5). You could move this to your.git/info/exclude.081c299There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bikeshedding a little here, but the advantage of putting it in
.gitignoreis that a Sublime user wouldn't have to do anything extra after they check out the repository. I think there are sufficiently many Sublime text users in the world to justify the change. We already have patterns specific to Emacs and Mac OS users.081c299There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bike shedding a little more here. :)
I'm a Sublime user, and never had to do anything extra for this repository before this commit. Now that it has a non-zero
.gitignorefile, I have to familiarize myself with it, and it ever-so-slightly increases the chance of there being some files in the repo without me realizing it becausegit statuswon't tell me. I prefer having as little content in repo's.gitignorefiles as possible because I find it lowers the mental overhead of tracking invisible/ignored files. Less is more.I don't feel strongly about this and nothing needs to be done, I just wanted to share my (slightly perfectionist, minimalist) POV and motivation for avoiding adding more content to
.gitignore. :)I am curious what other people think, whether they prefer empty
.gitignoresor all-encompassing ones like this or something in between, but perhaps this isn't the best place to hold this discussion. ;)081c299There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry! I'm happy to put this in my personal
.gitignore. Probably should have done that to begin with.