Skip to content
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

add .gitignore #21

Closed
wants to merge 1 commit into from
Closed

add .gitignore #21

wants to merge 1 commit into from

Conversation

andy5995
Copy link
Contributor

@andy5995 andy5995 commented Aug 8, 2019

No description provided.

@wmcbrine
Copy link
Owner

wmcbrine commented Aug 8, 2019

Ugh. This is a pet peeve of mine. I of course have a .gitignore... whose first line is ".gitignore". There's no reason for it to be in the repo.

@rswindell
Copy link
Contributor

The reason a .gitignore would be in the repo is so that not every single person who clones and rebuilds the repo would then be required rediscover all the possible build artifacts and create their own local .gitignore file so that their 'git status' output was reflective of the actual local changes. If you're going to be different from the norm and not have a .gitignore in your repo (which is totally your prerogative), stating so in your README.md file would be a nice clue to prevent future wasted time on this subject.

Repository owner locked and limited conversation to collaborators Oct 10, 2020
@wmcbrine
Copy link
Owner

Good grief.

@andy5995 andy5995 deleted the gitignore branch October 14, 2020 07:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants