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

Exclude build artifact files from 'git status' output. #27

Closed
wants to merge 1 commit into from

Conversation

rswindell
Copy link
Contributor

This file allows for a clean 'git status' report after running 'make'.

@wmcbrine
Copy link
Owner

I don't want .gitignore to be in the repo. I have a .gitignore file locally, and the first item in it is... ".gitignore".

@wmcbrine wmcbrine closed this Oct 10, 2020
@wmcbrine
Copy link
Owner

P.S. See #21

BTW, this is my actual .gitignore:

.gitignore
.DS_Store
*.o
*.obj
mm
mm.exe

Repository owner locked and limited conversation to collaborators Oct 10, 2020
Repository owner unlocked this conversation Oct 10, 2020
@rswindell
Copy link
Contributor Author

If you have multiple clones of the repo (as I usually do), you'd have to manually replicate that .gitignore file to each clone and deal with keeping them in-sync.

A comment in your README.md would hopefully prevent future wasted time on this matter.

@andy5995
Copy link
Contributor

andy5995 commented Oct 14, 2020

@rswindell I agree for the most part. Even if one doesn't work with multiple clones of a repo. I think .gitignore files are best used for projects/repos that aim to have contributors. I'm not sure if this one does or not (I didn't see a standard contributing doc or mention of contribution guidelines in the Readme). But basically, yeah, it saves time for collaborators in the long-run to have a "centralized" .gitignore, imo. But for projects with single or few maintainers, I'd agree with @wmcbrine that they aren't necessary.

@andy5995
Copy link
Contributor

@wmcbrine you might be interested to you know that you don't even need a .gitignore in your local repo.

If you transfer the current contents of your .gitignore to .git/info/exclude, you can then remove your .gitignore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants