Public documentation for Visual Studio Code
Перейти к файлу
Chuck Lantz 71ee2bdd80 Add clickable link into header of remote development extension guide 2019-05-07 17:06:45 -07:00
.vscode Commit LFS 2019-03-11 13:57:10 -07:00
api Add clickable link into header of remote development extension guide 2019-05-07 17:06:45 -07:00
blogs Update rich code nav blog post with Java 2019-05-05 18:56:38 -07:00
build Add remote topics to sitemap 2019-05-01 09:43:38 -07:00
docs Typo 2019-05-07 17:04:39 -07:00
images Commit LFS 2019-03-11 13:57:10 -07:00
release-notes Fix accessibility issue with duplicate h3 2019-05-02 16:30:43 -07:00
remote-release-notes Remote init 2019-04-03 15:12:08 -07:00
tutorials Remove topic 2019-04-19 16:27:20 -07:00
wiki/images Commit LFS 2019-03-11 13:57:10 -07:00
.editorconfig Commit LFS 2019-03-11 13:57:10 -07:00
.gitattributes Track gif, mp4, png and jpg files in lfs 2019-03-11 13:56:41 -07:00
.gitignore Commit LFS 2019-03-11 13:57:10 -07:00
CONTRIBUTING.md Fix README link 2019-03-12 10:21:33 -07:00
LICENSE.md Commit LFS 2019-03-11 13:57:10 -07:00
README.md fix 3.1 and 3.2 clauses 2019-05-07 09:45:58 -07:00
gulpfile.js Fix docs build 2019-05-02 10:47:28 -07:00
package.json Update lint-staged config 2019-03-25 15:57:05 -07:00
yarn.lock Precommit hook for git lfs. Fix #2506 2019-03-25 15:45:18 -07:00

README.md

vscode logo

Visual Studio Code Documentation

You've found the Visual Studio Code documentation GitHub repository, which contains the content for the Visual Studio Code documentation.

Topics submitted here will be published to the Visual Studio Code portal.

If you are looking for the VS Code product GitHub repository, you can find it here.

Index

  1. About Visual Studio Code
  2. Feedback
  3. Documentation Issues
  4. Contributing to the documentation
  5. Publishing

Visual Studio Code

VS Code is a lightweight source code editor and powerful development environment for building and debugging modern web and cloud applications. It is free and available on your favorite platform - Linux, macOS, and Windows.

If you landed here looking for other information about VS Code, head over to our website for additional information.

Feedback

If you want to give documentation feedback, please use the feedback control located at the bottom of each documentation page.

Documentation Issues

To enter documentation bugs, please create a new GitHub issue. Please check if there is existing issue first.

If you think the issue is with the VS Code product itself, please enter issues in the VS Code product repo here.

Contributing

To contribute with new topics / information or make changes to existing documentation, please read the Contributing Guideline.

Workflow

The two suggested workflows are:

  • For small changes, use the "Edit" button on each page to edit the Markdown file directly on GitHub.
  • If you plan to make significant changes or preview the Markdown files in VS Code, clone the repo to edit and preview the files directly in VS Code.

Markdown Preview Button

Cloning

  1. Install Git LFS.
  2. Run git lfs install to setup global git hooks. You only need to run this once per machine.
  3. git clone git@github.com:Microsoft/vscode-docs.git.
  4. Now you can git add binary files and commit them. They'll be tracked in LFS.

Cloning without binary files

You might want to clone the repo without the 1.6GB images. Here are the steps:

  1. Install Git LFS.
  2. Run git lfs install to setup global git hooks. You only need to run this once per machine.
  3. Clone the repo without binary files.
    3.1. macOS / Linux: GIT_LFS_SKIP_SMUDGE=1 git clone git@github.com:Microsoft/vscode-docs.git.
    3.2. Windows: $env:GIT_LFS_SKIP_SMUDGE="1"; git clone git@github.com:Microsoft/vscode-docs.git.
  4. Now you can selectively checkout some binary files to work with. For example:
    • git lfs pull -I "docs/nodejs"
    • git lfs pull -I "release-notes/images/1_3*/*"
    • You can do git lfs pull -I <PATTERN>, as long as <PATTERN> is comma-separated glob strings. For more patterns, see Git LFS: Include and Exclude.

The history of this repo before we adopted LFS can be found at microsoft/vscode-docs-archive.

Publishing

Steps for how to publish documentation changes can be found here in the (private) repository of the VS Code website.