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
Introduce .gitignore #24057
base: master
Are you sure you want to change the base?
Introduce .gitignore #24057
Conversation
maybe also .patch in the root directory? |
I'm a little bit unsure, whether this is really required. Just for reference: |
Well, the headline could be somehow true, I am not saying that it is wrong, but even there is some discussion in comments below the article Anyway, Also, it was requested to have |
Yes, this is a controversial topic. There are arguments for and against. Personally, I don't think it's necessary, but I'm not totally against it either. |
@mhei my 2 cent are that .vscode might be handy for single project repository where it would be beneficial to have vscode or editors in general setup for the project. For this specific case where these are a sum of many Makefile and project... I can't find a way where .vscode would be beneficial... With all the variety of code and style we have I think there isn't a common option for everyone. |
This file specifies files that Git should ignore while creating commit. Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
There 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.
I'm fine with this PR.
This PR adds file
.gitignore
to this repository.