aboutsummaryrefslogtreecommitdiffstats
path: root/Global/VisualStudioCode.gitignore
Commit message (Collapse)AuthorAgeFilesLines
* Ignore files in directory, not the directory itselfAndrew Shymanel2021-12-141-1/+1
|
* Merge pull request #3788 from SethFalco/patch-1Brian Douglas2021-12-101-0/+3
|\ | | | | VisualStudioCode: ignores built vscode extensions
| * VisualStudioCode: ignores built vscode extensionsSeth Falco2021-07-201-0/+3
| |
* | Merge pull request #3839 from tropicalraisel/patch-1Brian Douglas2021-12-101-1/+1
|\ \ | | | | | | Fixed .vscode not being ignored
| * | Fixed .vscode not being ignoredTropical Raisel2021-09-271-1/+1
| |/
* | Update VS Code to support *.code-snippetsTim2021-12-101-0/+1
| |
* | Make not to ignore *.code-workspace방성범 (Bang Seongbeom)2021-09-181-1/+0
|/ | | | | | | | | | | **Reasons for making this change:** Workspace file can allow you to have an individual VS Code setting file for each project, which is useful for monorepo-based development. You can find an example on [lit/lit/lit-next.code-workspace](https://github.com/lit/lit/blob/08f60328abf83113fe82c9d8ee43dc71f10a9b77/lit-next.code-workspace). **Links to documentation supporting these rule changes:** https://code.visualstudio.com/docs/editor/multi-root-workspaces#_workspace-file
* Ignore Local History folder (#3008)ofthelit2020-04-041-0/+3
| | | | This will add support for the default location the Local History extension for Visual Studio Code uses. See https://marketplace.visualstudio.com/items?itemName=xyz.local-history
* Update to Global/VisualStudioCode (#3201)Jens Kürschner2019-10-101-0/+1
| | | Added ignore for workspace files (*.code-workspace). They can be added in any directory, depending on the user's preferences.
* Modified VS Code .gitignoreDavor Mas2016-11-211-0/+1
| | | | | Added extensions.json as exception in .vscode folder. File is used as extensions recommendation for project.
* Update Visual Studio Code to support workspace files.Brennan Fee2016-08-041-2/+4
| | | | | | | Visual Studio Code has a few files that can be placed into the workspace in order to share settings across users. Settings.json is for project specific overrides. Tasks.json is for executable tasks (build, gulp, etc.) While launch.json is for debugging specific tasks.
* VSCode 0.8.0 config folder changeBenjamin Pasero2015-08-311-1/+1
| | | Starting with 0.8.0, VS Code will store its settings in a .vscode folder and no longer in the generic .settings folder.
* Move VS Code to Global folderVictor Isadov2015-05-021-0/+2