-
-
Notifications
You must be signed in to change notification settings - Fork 82
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 initial IDE setup #1326
Add initial IDE setup #1326
Conversation
So your argument for removing .vscode is that they have no reuse value to anyone else, and are strictly for the author's local environment? I don't know enough about VSCode configurations to say for sure, but it looks like they're attempting to set up a debugging environment. For those who are using VSCode, I can see two additional actions we want to take here:
Thoughts? |
It's the same with all of these IDE/environment-specific files: They are specific to your personal setup. If you check them in, you destroy/overwrite the environment of somebody else. If somebody else modifies these files, the changes are forced upon your environment. Very annoying! |
I just noticed that the .gitignore files checked in contain several items that may not belong there. Also items added by me, e.g. ".settings", ".cproject", used by Eclipse. |
Kudos, SonarCloud Quality Gate passed! |
I had to read up on how to do local machine only .gitignore rules. What I learned is that the git manual recommends using .git/info/exclude https://git-scm.com/docs/gitignore#_description I agree that this is better than trying to anticipate every single IDE behavior. |
There is yet one more argument not to have IDE configurations checked in: Their format depends on the IDE version. |
No description provided.