X Tutup
The Wayback Machine - https://web.archive.org/web/20210210104042/https://github.com/github/gitignore/pull/3549
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

Update Node.gitignore #3549

Open
wants to merge 1 commit into
base: master
from
Open

Update Node.gitignore #3549

wants to merge 1 commit into from

Conversation

@heclack
Copy link

@heclack heclack commented Oct 12, 2020

Reason:
Personal IDE settings do not belong in code base.

documentation of ".vscode" file:
https://code.visualstudio.com/docs/getstarted/settings

If this is a new template:

  • Link to application or project’s homepage: N/A
Propose adding .vscode to gitignore=> I can see how passing along your vscode workspace setting could be nice to someone working on the same project.  However, because
1. .vscode is often automatically generated by vscode application
2.  .vscode is application specific file 
3. .vscode is meant (i speak from a linux standpoint) is meant to be hidden
.vscode should be on the template default .gitignore.
@Jabster28
Copy link

@Jabster28 Jabster28 commented Oct 21, 2020

Personal IDE settings would be in the user settings, no? I feel like the workspace settings are meant to enforce code styles and what not.

@53jk1
53jk1 approved these changes Oct 23, 2020
@heclack
Copy link
Author

@heclack heclack commented Oct 25, 2020

Yes, but by tying settings into a specific editing application are you not forcing anyone who works on the codebase to use vscode? Is that an appropriate precedent to set, especially considering git version-control is used very often in open source codebase?

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

Successfully merging this pull request may close these issues.

None yet

3 participants
X Tutup