Upload folder using huggingface_hub

.editorconfig

@@ -0,0 +1,5 @@
+root = true
+
+[*]
+end_of_line = lf
+trim_trailing_whitespace = true

.gitattributes

@@ -33,3 +33,649 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zst filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
+api/extension-capabilities/images/extending-workbench/workbench-contribution.png filter=lfs diff=lfs merge=lfs -text
+api/extension-capabilities/images/theming/color-theme.png filter=lfs diff=lfs merge=lfs -text
+api/extension-capabilities/images/theming/icon-theme.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/color-theme/color-setting.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/color-theme/tm-inspector.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/debugger-extension/debug-features.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/debugger-extension/debugger-extension-server.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/debugger-extension/mock-debug.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/tree-view/view-container.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-developer_tools.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-drag.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-html.png filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-ondidchangeviewstate.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-restore.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-single_panel.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/basics-update.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/persistence-retrain.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/scripts-basic.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/scripts-extension_to_webview.gif filter=lfs diff=lfs merge=lfs -text
+api/extension-guides/images/webview/scripts-webview_to_extension.gif filter=lfs diff=lfs merge=lfs -text
+api/get-started/images/your-first-extension/debug.mp4 filter=lfs diff=lfs merge=lfs -text
+api/get-started/images/your-first-extension/launch.mp4 filter=lfs diff=lfs merge=lfs -text
+api/get-started/images/your-first-extension/reload.mp4 filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-server-extension-guide/debugging-client.png filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-server-extension-guide/debugging-server.png filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-server-extension-guide/lsp-inspector.png filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-server-extension-guide/lsp-log.png filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/code-completion.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/code-lens[[:space:]]copy.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/code-lens.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/document-highlights.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/document-symbols.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/find-references.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/format-document-range.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/format-document.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/goto-definition.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/hovers.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/quick-fixes.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/rename.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/language-support/workspace-symbols.gif filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/syntax-highlighting/yaml-grammar.png filter=lfs diff=lfs merge=lfs -text
+api/language-extensions/images/syntax-highlighting/yo-new-language-questions.png filter=lfs diff=lfs merge=lfs -text
+api/references/images/contribution-points/menus.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/continuous-integration/pipelines.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/publishing-extension/token1.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/publishing-extension/token2.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/publishing-extension/token3.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/publishing-extension/token4.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/testing-extension/pipelines.png filter=lfs diff=lfs merge=lfs -text
+api/working-with-extensions/images/testing-extension/test-output.png filter=lfs diff=lfs merge=lfs -text
+blogs/2016/02/23/chrome-debugger-demo.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/03/11/change-case_demo.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/03/11/ruby_debugging.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/03/11/yo_demo.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/04/14/header.png filter=lfs diff=lfs merge=lfs -text
+blogs/2016/04/14/installs.png filter=lfs diff=lfs merge=lfs -text
+blogs/2016/05/04/auto-complete.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/05/04/complexity-codelens.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/05/04/debugger-for-edge.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/05/04/svg-viewer.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/07/29/annotate-animation.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/07/29/git-history-animation.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/07/29/partial-diff.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/07/29/share-code-animation.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/08/19/github_reaction.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/08/22/ios-debugger-demo.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/09/14/npm_intellisense.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/10/31/chrome_debugger.png filter=lfs diff=lfs merge=lfs -text
+blogs/2016/10/31/document_this.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/10/31/git_project_manager.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2016/12/12/theme-preview.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/01/15/AppSettings.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/01/15/AzurePortal.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/01/15/ChromePause.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/01/15/CreateDocDB.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/01/15/Debugger.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/01/15/Dockerfile.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/02/08/TM-scope-inspector.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/02/08/tokenization-2.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/02/12/code_lens.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/02/12/manifest_preview.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/02/12/preview_gitlens.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/04/10/close_html_xml_tag.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/06/20/themes-ayu.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/06/20/themes-nord.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/06/20/themes-sapphire.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/06/20/vscode-great-icons.jpg filter=lfs diff=lfs merge=lfs -text
+blogs/2017/08/07/emmet.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/09/28/java-debug.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/10/03/60fps.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/10/03/paint-flashing.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/10/03/texture-atlas.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/10/24/stablewithblue.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/11/15/ls-dual-screen.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/11/15/ls-social-resized.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/11/15/ls-social.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/11/15/vs-code-ls-session.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/11/15/vs-code-ls-session2.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/12/20/break_on_load_after.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/12/20/code_chrome_devtools.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2017/12/20/social_paused.png filter=lfs diff=lfs merge=lfs -text
+blogs/2017/12/20/sync_stepping.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/03/23/piece-tree.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/03/23/write.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/04/25/Beautify.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/04/25/BingDiagram.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/04/25/FormatOnKeypress.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/04/25/OpenFilesOnLeft.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/04/25/SocialImg.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/04/25/ZoomScrollWheel.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/05/07/lsp.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/05/07/shared-terminal.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/07/12/auto-attach.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/07/12/debug-extension-api.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/07/12/debugger.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/07/12/debugging_architecture.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/07/12/logpoints.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/07/12/npm_scripts.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/09/10/github_pr_hero.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/09/10/github_pr_overview.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/09/12/build.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/09/12/pr.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/09/12/slack.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/09/12/tweet.png filter=lfs diff=lfs merge=lfs -text
+blogs/2018/12/04/CPlusPlus.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/12/04/CSharp.gif filter=lfs diff=lfs merge=lfs -text
+blogs/2018/12/04/CrossRepoJump.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/docker/dockercommands.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/docker/generateFiles.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/kubernetes/check-status.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/kubernetes/create-k8s.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/kubernetes/create-manifest.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/kubernetes/install-kubernetes.png filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/kubernetes/start-deployment.gif filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/remote-debugging/remote-breakpoint.png filter=lfs diff=lfs merge=lfs -text
+docs/azure/images/remote-debugging/start-remote-debugging.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/accessibility/zoomed-in.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/codebasics/CodeBasics.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/codebasics/column-select.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/codebasics/multicursor-word.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/codebasics/multicursor.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/debugging/Debugging.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/debugging/add-config.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/debugging/hitCount.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/debugging/launch-json-intellisense.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/debugging/log-points.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/emmet/emmet-multi-cursor.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/emmet/emmet-vendor-prefix.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/emmet/emmet.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/disable-extension.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/enable-extension.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/extension-search-categories.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/extensions-disable-all.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/extensions-disable.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/extensions-popular.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/extensions-python.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/extension-gallery/uninstall-extension.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/intellisense/localitybonus.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/intellisense/tabCompletion.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/multi-root-workspaces/multiple-scm-providers.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/multi-root-workspaces/settings-dropdown.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/refactoring/ts-extract-local.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/tasks/run-input-example.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/userdefinedsnippets/ajax-snippet.gif filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/versioncontrol/GitHub-clone-dialog.png filter=lfs diff=lfs merge=lfs -text
+docs/editor/images/versioncontrol/scm.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/keybinding/keyboard-shortcuts.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/settings/lang-based-settings.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/themes/built-in-themes.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/themes/theme-activitybar.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/Errors_Warnings.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/InstallExtensions.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/KeyboardShortcuts.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/OpenCommandPalatte.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/PreviewFileIconThemes.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/PreviewThemes.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/QuickOpen.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/add_cursor_current_selection.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/add_cursor_current_selection_one_by_one.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/change_syntax.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/code_folding.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/code_formatting.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/column-select.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/command_p.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/configure_debug.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/create_open_file.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/debug_data_inspection.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/emmet_syntax.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/find_all_references.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/find_by_symbol.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/git_side_by_side.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/git_stage_all.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/goto_definition.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/intellisense.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/markdown-preview-side-by-side.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/move_line.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/multicursor.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/navigate_editors.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/navigate_history.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/navigate_to_line.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/node_debug.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/package_json_intellisense.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/peek.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/rename_symbol.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/shrink_expand_selection.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/split_editor.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/switch_branches.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/task_runner.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/toggle_side_bar.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/trim_whitespace.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/undo_last_commit.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/tips-and-tricks/zen_mode.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/grid-dnd.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/grid-layout-menu.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/grid-layout.gif filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/hero.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/sidebyside.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/tabs-editor-groups.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/view-management.png filter=lfs diff=lfs merge=lfs -text
+docs/getstarted/images/userinterface/workspace-settings.png filter=lfs diff=lfs merge=lfs -text
+docs/introvideos/images/opengraph/introvideos.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-azurefunctions/add-functions.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-azurefunctions/debug-functions.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-azurefunctions/deploy-functions.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/attach-source.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/conditional-bp.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/current-file.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/cwd-env.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/expression-evaluation.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/hcr.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/java-debug.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/java9.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/junit.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/launch-in-terminal.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/logpoints.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/resolve-main.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/single-file.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/step-filter.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-debugging/test-explorer.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/Intellisense(Intellicode).gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/checkstyle.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/code-editing.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/getter-setter.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/intellicode.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/quick-fix.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/refactor.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/rename.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/search-in-file.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/search-in-workspace.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-editing/spring-navigation.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/create-project.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/hierarchical.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-archetype.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-effective-pom.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-explorer.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-history.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-plugin-goal.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-pom-editing.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/maven-run.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/multiple-source.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/package-viewer.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-project/standalone.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-spring-boot/spring-code-edit.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-spring-boot/spring-dashboard.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-spring-boot/spring-initializr-edit.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-spring-boot/spring-initializr.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-testing/report.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-testing/test-junit5.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-testing/testng.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-tomcat-jetty/jetty.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-tomcat-jetty/tomcat-create-server.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-tomcat-jetty/tomcat.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-tutorial/create-file.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-tutorial/edit-code.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-tutorial/run-debug.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-webapp/clone-repository.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-webapp/debugging-status-bar.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-webapp/debugging.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-webapp/deploy-webapp.png filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-webapp/install-extensions.gif filter=lfs diff=lfs merge=lfs -text
+docs/java/images/java-webapp/run-spring-boot.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/Markdown/double-click-preview-switch.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/Markdown/md-dynamic-preview.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/Markdown/preview-scroll-sync.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/Markdown/security-alert.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/cpp/includepath.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/cpp/languages_cpp.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/csharp/languages_csharp.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/html/auto-close1.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/html/emmetsnippet.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/intellisense.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/java-debug.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/java-test-explorer.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/java-test.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/package-viewer.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/resolve-main.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/testng.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/tomcat.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/java/vscode-java.0.0.1.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/checkjs-example.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/intellisense-placeholder.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/intellisense.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/jsx.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/organize-imports.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/overview.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/tag-complete.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/update-imports-placeholder.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/javascript/update-imports.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/powershell/codeLensFuncRef.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/powershell/codeLensPesterDebug.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/powershell/codeLensPesterSymbol.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/python/feature_showcase.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/python/jupyter.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/python/python-debugging.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/python/python-editing.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/python/python-linting.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/python/python-snippets.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/tsql/execute.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/tsql/intellisense.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/tsql/linting.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/tsql/peekdefinition.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/tsql/save.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/tsql/snippets.gif filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/typescript/Languages_typescript.png filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/typescript/intellisense.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/typescript/jsdoc-autofill.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/typescript/jsx-tag-complete.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/typescript/organize-imports.mp4 filter=lfs diff=lfs merge=lfs -text
+docs/languages/images/typescript/overview.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/emberjs/welcome-page.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/extensions/chrome_debugger.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/extensions/document_this.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/extensions/npm_intellisense.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs/debugsession.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs/hello-world-debugging.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs/runtimes_node.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs-debugging/auto-attach-cluster.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs-debugging/auto-attach.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs-debugging/loaded-scripts-explorer.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/nodejs-debugging/loaded-scripts.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/reactjs/hit-breakpoint.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/recipes/chrome.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/recipes/electron.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/recipes/mern.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/recipes/node-typescript-docker.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/recipes/nodejs.png filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/working-with-javascript/checkjs-example.gif filter=lfs diff=lfs merge=lfs -text
+docs/nodejs/images/working-with-javascript/disable-TS-language.png filter=lfs diff=lfs merge=lfs -text
+docs/other/images/office/yoofficemanifest.png filter=lfs diff=lfs merge=lfs -text
+docs/other/images/unity/wow.gif filter=lfs diff=lfs merge=lfs -text
+docs/python/images/debugging/debugGAE.gif filter=lfs diff=lfs merge=lfs -text
+docs/python/images/deploy-containers/deploy-to-app-service.gif filter=lfs diff=lfs merge=lfs -text
+docs/python/images/editing/python-editing.gif filter=lfs diff=lfs merge=lfs -text
+docs/python/images/editing/refactorExtractMethod.gif filter=lfs diff=lfs merge=lfs -text
+docs/python/images/jupyter/jupyter-notebook.png filter=lfs diff=lfs merge=lfs -text
+docs/setup/images/mac/touchbar.gif filter=lfs diff=lfs merge=lfs -text
+docs/setup/images/quicksetup/QuickSetup.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/0_10_0/hello-code.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/0_8_0/colorthemes.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/column-breakpoints.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/copy-with-syntax-highlighting.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/drag-and-drop.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/jsdoc-autofill.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/launch-keyboard.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/minimap-blocks-scroll.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_10/minimap.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/abyss-theme.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/color-settings.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/config-exceptions.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/exception-peekui.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/keyboard-shortcuts.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/loaded-scripts.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_11/panel.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/column-breakpoints.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/completions-dynamic-sort.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/keyboard-shortcuts-editor.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/native-tabs.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/terminal-line-col-link.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/theme-activitybar.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/theme-generator.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_12/ts-checkjs-example.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/emmet.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/high-contrast.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/jsx-new-coloring.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/letter-spacing.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/markdown-heading-levels.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/new-setting-defaults.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/resize-find-widget.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/snippets-multi-cursor.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/step-after.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/step-before.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/suggest.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/task-customize.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/terminal-vtop-after.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/terminal-vtop-before.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_13/uncover-matched-results.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/commands-history.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/emmet.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/empty-window-restore.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/github-issues-and-prs.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/gitignore.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/js-refactoring.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/minimap-horizontal-slider.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/quick-switch-windows.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/tasks-matcher-attach.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/terminal-selection-select.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_14/ts-build-task.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/folder_settings.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/loaded-scripts-explorer.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/markdown-preview-search.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/markdown-security.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/react-tutorial.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/snippet-choice.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/views_management.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/workspace.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_15/workspace_settings.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/auto-close1.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/eh-breakpoints.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/exthost-restart.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/folder-drop.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/multi-root-dnd.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/multi-root-transition.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/scm-multiroot.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/search-dnd.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/smooth-scrolling.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_16/ts-extract.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/console_messages.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/js-markdown-intellisense.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/markdown-fenced-commenting.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/offside-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/quick-suggestion-path-intellisense.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/region-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/scm.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/terminal_60fps.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/touchbar.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_17/wait.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/diff.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/git-decorations.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/merge.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/multiroot.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/panel-title.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/recommendationinstall-configure.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/recommendations-badge.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/string-quick-suggestions.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/ts-extract-local.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_18/vertical-panel.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_19/image-diff.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_19/shrink.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_19/status.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_19/stdin.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_19/suggest_mem.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_19/vscode-processes.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/auto-attach-cluster.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/emmetprefix.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/filerec.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/git-input-validation.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/image-zoom.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/minimap-left-side.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/multi-select.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/output-log-channels.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/popular-extension.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/save_admin.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/submodules.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/tab_hover.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/toggle-ignore-trim-whitespace.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_20/ts-auto-import-default.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/centeredLayout.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/emmet-style.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/manage-builtin.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/md-dynamic-preview.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/md-scroll-sync.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/notifications.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/path-completion.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/search.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/terminal-split.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/window-copy-paste.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_21/window-dnd-files.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/auto-attach.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/f8-navigation.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/log-points.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/markdown-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/references-f4.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/related-diagnostics-information.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/save_part.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/syntax-fold.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/syntaxhighlight-optimization.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/terminal-command-tracking.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/ts-jsdocs-quicksuggestions.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/ts-organize-imports.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_22/wrap.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/SublimeSettingsImporter.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/active-indent-guide.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/copy-search.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/css-csstree.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/css-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/css-mdn.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/editor-column-select.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/editor-stability.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/fsp.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/logpoints.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/markdown-restore.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/problems_filter.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/process-explorer.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_23/webview.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/debug_toolbar.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/grid.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/inline-diff-syntax.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/outline-all.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/scss-at.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/settings-editor.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/ts-import-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/ts-move-to-file-post.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/ts-move-to-file-pre.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_24/ts-update-imports.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/debugtoolbar.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/defaultExtensionsView.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/drop.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/editor-sub-word-navigation.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/editorPaneBackground.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/grid-dnd.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/grid-layout.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/lsp-inspector.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/multistepinput.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/settings-editor.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_25/snippet_placeholder_transform.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/breadcrumbs_active.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/breadcrumbs_tabs_notabs.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/extension-intellisense.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/grid-maximize.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/multistepinput.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/open-folder-uri.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/quickfix-problems.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/rapid_render.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/settings-editor.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/terminal-column-selection.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/ts-convert-to-namespace-import.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/ts-import-all-quick-fix.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/ts-jsx-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/ts-jsx-tag-complete.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_26/webview-icon.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/css-definition.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/css-import.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/extension-settings.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/github_pull_requests.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/log-streaming.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/picker-highlights.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_27/search-filter.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/comment_edit.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/deleted.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/markdown-folding.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/markdown-preview-link.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/record-keybindings.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/tabcompletion.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/ts-convert-to-async.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_28/ts-rename-import.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/file-icon-preview.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/highlight-modified-tabs.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/json-schema-loading.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/mojave-dark.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/multiline.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/references-view.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_29/workbench-navigation.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/api-sighelp-context.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/custom-title-menu-linux.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/debug-from-process-explorer.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/downgrade-Extension.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/exthost-slow-the-movie.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/go-to-declaration.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/html-custom-tag-attribute.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/input-example.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/references-viewlet.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/settings-actions.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/ts-new-callback-nav.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/ts-new-quickfix.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/ts-old-callback-nav.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_30/ts-rename.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/api-toc.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/customdata.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/html-css-json-selection.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/live-theme-editing.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/no-reload-language-extension.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/problems-multi-line.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/ref-history.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/screencast.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/select-all.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/smart-select-demo.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/terminal-cwd-links.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/terminal-reflow.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_31/type-filter.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/column-selection-alt-key.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/debug-console-font.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/html-attribute-completion.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/keyboard-shortcuts-when.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/problem-hover.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/server-ready.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/theme-install.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_32/vetur-intellisense-vue-template.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_7/hitCount.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_7/horizontal.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_7/multiDebug.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_8/add-config.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_8/hide-activitybar.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_8/javascript-in-html.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_8/quick-edit-settings.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_8/search-settings.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_8/viewlet.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/configure-lang-mode.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/inline_values.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/log-objects.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/markdown-double-click-preview-switch.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/markdown-preview-to-editor-scroll-sync.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/markdown-selection-preview-scroll-sync.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/no_folder_debug.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/search-result-nav.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/settings.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/tasks.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/terminal-after.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/1_9/toggle-skip-file.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/April/smartStepping.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/February/function-breakpoint.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/February/high-contrast.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/January/api-virtual-documents.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/July_2016/insertSnippet.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/July_2016/restartFrame.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/July_2016/tabCompletion.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/dnd_editor.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/editor-mouse-wheel-zoom.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/extensions_viewlet.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/multiline-find.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/searchAndReplace.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/social.jpg filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/stacks.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/June_2016/tabs.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/March/column-select-mouse.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/March/extension-widget.png filter=lfs diff=lfs merge=lfs -text
+release-notes/images/May_2016/peek.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/May_2016/selectAllFindMatches.gif filter=lfs diff=lfs merge=lfs -text
+release-notes/images/May_2016/tabsprogress.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/docker-extension/create.gif filter=lfs diff=lfs merge=lfs -text
+tutorials/images/functions-extension/function-debugging.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/functions-extension/functions-vscode-intro.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/nodejs-deployment/emptyazuresite.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/nodejs-deployment/searchforextension.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/nodejs-deployment/sqlextension.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/static-website/azure-app.png filter=lfs diff=lfs merge=lfs -text
+tutorials/images/static-website/updated-azure-app.png filter=lfs diff=lfs merge=lfs -text

.gitignore

@@ -0,0 +1,10 @@
+_build
+node_modules
+
+.DS_Store
+.vscode/spell.json
+
+.idea
+
+*.sublime-project
+*.sublime-workspace

.vscode/settings.json

@@ -0,0 +1,9 @@
+// Place your settings in this file to overwrite default and user settings.
+{
+    "editor.wordWrap": "on",
+    "files.eol": "\n",
+    "files.trimTrailingWhitespace": true,
+    "files.associations": {
+        "**/toc.json": "jsonc"
+    }
+}

CONTRIBUTING.md

@@ -0,0 +1,188 @@
+# Visual Studio Code Documentation
+
+You've found the GitHub repository that houses the source for the VS Code docs at <https://code.visualstudio.com/docs>.
+
+## Contribute to VS Code documentation
+
+Thank you for your interest in VS Code documentation!
+
+* [Contributing](#contributing)
+* [Documentation intent](#documentation-intent)
+* [Repository organization](#repository-organization)
+* [Branches](#branches)
+* [Authoring Tools](#authoring-tools)
+* [How to use Markdown to format your topic](#how-to-use-markdown-to-format-your-topic)
+* [Topic Metadata](#topic-metadata)
+* [Formatting](#formatting)
+
+>**Note**: Before submitting a pull request, especially for rendering or link issues, please review the content on the official VS Code website, [code.visualstudio.com](https://code.visualstudio.com). The element in question may render correctly after processing by the website build.
+
+## Contributing
+
+To contribute to [VS Code documentation](https://code.visualstudio.com/docs), you need to fork this repository and submit a pull request for the Markdown and/or image changes that you're proposing.
+
+* [How to fork a repository](https://help.github.com/articles/fork-a-repo)
+* [How to make a pull request](https://help.github.com/articles/creating-a-pull-request/)
+* [Changing a commit message](https://help.github.com/articles/changing-a-commit-message/)
+* [How to squash commits](https://help.github.com/articles/about-pull-request-merges/)
+
+## Documentation intent
+
+The goal of the VS Code documentation is to educate users on VS Code features and how VS Code can be used to enhance their development experience with different programming languages and runtimes.
+
+The documentation is not intended to provide:
+
+* An introduction to coding or software development
+* Tutorials on technologies independent from VS Code
+* Promotion of third-party tools, plug-ins or services
+* Excessive detail or advanced walkthroughs
+
+The documentation should target developers learning to use VS Code or searching for quick answers to commonly asked questions.  Other forums such as blog posts can provide more detailed content elaborating on specific scenarios.
+
+## Repository organization
+
+The content in this repository follows the organization of documentation at <https://code.visualstudio.com/docs>.
+
+This repository contains the following folders:
+
+* \setup
+* \introvideos
+* \getstarted
+* \editor
+* \languages
+* \extensions
+* \extensionAPI
+* \other
+* \supporting
+
+Within these folders you'll find the Markdown files used for the content. Each of these folders also contains an \images folder that references the images (such as screenshots) used in the topics.
+
+### Branches
+
+We recommend that you create local working branches that target a specific scope of change (and then submit a pull request when your changes are ready). Each branch should be limited to a single concept/topic, both to streamline work flow, and to reduce the possibility of merge conflicts.  The following efforts are of the appropriate scope for a new branch:
+
+* A new topic (and associated images).
+* Spelling and grammar edits on a topic.
+* Applying a single formatting change across a large set of topics.
+
+## Authoring tools
+
+[Visual Studio Code](https://code.visualstudio.com) is a great editor for Markdown!
+
+In fact, VS Code and its core documentation are written using VS Code.
+
+## How to use Markdown to format your topic
+
+The topics in this repository use Markdown.  Here is a good overview of [Markdown basics](https://help.github.com/articles/markdown-basics/).
+
+## Topic Metadata
+
+Topic metadata enables certain functionalities for the topics such as table of contents order, topic descriptions, and online search optimization as well as aiding Microsoft in evaluating the effectiveness of the content.
+
+* **Order** - This is the order that is used in the left rail TOC, the page is left out of the TOC if this is blank
+* **Area** - General area within VS Code
+* **TOCTitle** - The title used in the left rail Table of Contents for this page
+* **PageTitle** - The title used in the HTML title for the page and in search results
+* **ContentId** - A GUID which uniquely identifies the topic to DevDiv doc reporting.
+* **DateApproved** - This is set when the page is actually published on the VS Code portal. You can ignore it.
+* **MetaDescription** - The meta description for this page which helps for search. Use sentence structure limited to 300 characters.
+* **MetaSocialImage** - Optional. Used for og:image in page header for sharing on social media. Should be 1024 x 512 .png.
+* **MetaTags** - Optional. Further tags for this page again for search.
+
+## Product name
+
+Use the full product name "Visual Studio Code" in the topic MetaDescription and the first use in a topic. You can use the shortened "VS Code" after that throughout the rest of the content. Do not use "VSCode" (no space) or "Code".
+
+### Metadata for /api docs
+
+**For Writer**:
+
+* **MetaDescription** - The meta description for this page which helps for search
+
+**For Doc Maintainer**:
+
+* **DateApproved** - This is set when the page is actually published on the VS Code portal.
+
+## Formatting
+
+### Headings & Right Nav
+
+H2 subheadings `##` end up in the right hand jump list for the document (this happens in our compile script).  It's a good idea to include h2 subheadings to help users get an overview of the doc and quickly navigate to the major topics.
+
+### Text formatting
+
+Use bold for VS Code commands and UI elements.
+
+    **Extensions: Install Extension**
+    **Debug Console**
+
+Limit the use of bold for emphasis unless it is crucial to get the user's attention. Avoid the use of italics for emphasis since italics doesn't render well on the code.visualstudio.com site.
+
+Use inline code formatting (backticks) for settings, filename and JSON attributes.
+
+    `files.exclude`
+    `tasks.json`
+    `preLaunchTask`
+
+Use '>' to show menu sequence.
+
+    **File** > **Preferences** > **Settings**
+    **View** > **Command Palette**
+
+### Links
+
+For links within our own documentation, use a site relative link like `/docs/editor/codebasics.md`.
+
+>For example: `[Why VS Code](/docs/editor/whyvscode.md)` - links to the **Why Visual Studio Code** page
+
+>**Correction:** For this repo to ease content development you should add the .md suffix.  We will parse these out for the website deployment.
+
+### Bookmarks
+
+To provide links to h2 subheadings (Markdown ##), the format is `[Link Text](page.md#subheading-title)`.
+
+Note the subheading title is lowercase and subheading title words are separated by '-' hyphens.
+
+>For example: `[Keyboard Shortcuts](/docs/editor/codebasics.md#keyboard-shortcuts)` - links to https://code.visualstudio.com/docs/editor/codebasics#_keyboard-shortcuts.
+
+### Images
+
+Images are important to bring the product to life - even if people can't try the product, these really help them to see what they are missing.
+
+For images you're adding to the repo, store them in the `images` subfolder of the TOC section, for example: `editor\images\debugging`.
+
+When you link to an image, the path and filename are case-sensitive.  The convention is for image filenames to be all lowercase.
+
+>For example: `![Debug Breakpoints](images/debugging/breakpoints.png)`
+
+### Key bindings
+
+The VS Code portal is able to show the correct key bindings depending on the reader's operating system (macOS, Windows or Linux).
+
+To enable this for keyboard shortcuts, use the format `kb(workbench.action.files.openFile)` where the command name is included in parentheses.
+
+>For a list of key bindings and the relevant `Command Ids` review the [key bindings document](https://code.visualstudio.com/docs/getstarted/keybindings).
+
+If you are listing out multiple key bindings, you can use a table.
+
+>Shortcut|Key Strokes
+>--------|-----------
+>Cut|`kb(editor.action.clipboardCutAction)`
+>Copy|`kb(editor.action.clipboardCopyAction)`
+>Paste|`kb(editor.action.clipboardPasteAction)`
+
+### Source Code
+
+For source code we use the fenced code block notation ```` ``` ````.
+
+>**Note:** You can add an optional language identifier to enable syntax highlighting in your fenced code block. E.g. ```` ```json ```` or ```` ```javascript ````. [Read more →](https://help.github.com/articles/creating-and-highlighting-code-blocks/#syntax-highlighting)
+
+Some JavaScript code...
+
+```javascript
+function fancyAlert(arg) {
+  if (arg) {
+    $.facebox({ div: foo });
+  }
+}
+```

LICENSE.md

@@ -0,0 +1,6 @@
+Copyright (c) Microsoft Corporation. All rights reserved. Distributed under the following terms:
+
+1.	Documentation is licensed under the [Creative Commons Attribution 3.0 United States License](https://creativecommons.org/licenses/by/3.0/us/legalcode). Code is licensed under the [MIT License](https://opensource.org/licenses/MIT).
+
+2.	This license does not grant you rights to use any trademarks or logos of Microsoft. For Microsoft’s general trademark guidelines, go to  https://go.microsoft.com/fwlink/?LinkID=254653.
+

README.md

@@ -0,0 +1,66 @@
+<center>
+<img alt="vscode logo" src="https://upload.wikimedia.org/wikipedia/commons/thumb/2/2d/Visual_Studio_Code_1.18_icon.svg/1200px-Visual_Studio_Code_1.18_icon.svg.png" width="100px">
+</center>
+
+# Visual Studio Code Documentation
+
+You've found the Visual Studio Code documentation GitHub repository, which contains the content for the [Visual Studio Code documentation](https://code.visualstudio.com/docs).
+
+Topics submitted here will be published to the [Visual Studio Code](https://code.visualstudio.com) portal.
+
+If you are looking for the VS Code product GitHub repository, you can find it [here](https://github.com/Microsoft/vscode).
+
+## Index
+1. [About Visual Studio Code](#visual-studio-code)
+2. [Contributing to the documentation](#contributing-to-the-documentation)
+3. [Feedback](#feedback)
+4. [Documentation Issues](#documentation-issues)
+5. [Editing](#editing)
+6. [Publishing](#publishing)
+
+## Visual Studio Code
+
+[VS Code](https://code.visualstudio.com/) 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](https://code.visualstudio.com) for additional information.
+
+## Contributing to the documentation
+
+To contribute with new topics/information or make changes to existing documentation, see [contributing](https://github.com/Microsoft/vscode-docs/blob/master/CONTRIBUTING.md#contributing) for instructions and guidelines.
+
+## 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](https://github.com/Microsoft/vscode-docs/issues) (try to check if there isn't a topic about your issue already).
+
+If you think the issue is with the VS Code product itself, please enter issues [here](https://github.com/Microsoft/vscode/issues).
+
+## Editing
+
+In order to edit the VS Code documentation, ensure that you have [Git](https://git-scm.com/downloads) installed.
+
+Clone a copy of the repo:
+
+```
+git clone https://github.com/Microsoft/vscode-docs.git
+```
+
+VS Code itself is great for reviewing and editing [Markdown](https://code.visualstudio.com/docs/languages/markdown) with nice preview support.
+
+If you want to use VS Code, simply navigate to the `vscode-docs` directory and launch VS Code from there:
+
+```
+cd vscode-docs
+code .
+```
+
+You can open any of the Markdown files and see a preview with the **Open Preview to the Side** button in the upper right of the editor.
+
+![Markdown Preview Button](images/MDPreviewButton.png)
+
+## Publishing
+
+Steps for how to publish documentation changes can be found [here](https://github.com/Microsoft/vscode-website#publishing-a-documentation-change) in the (private) repository of the VS Code website.

api/.prettierrc.json

@@ -0,0 +1,5 @@
+{
+  "printWidth": 92,
+  "tabWidth": 2,
+  "singleQuote": true
+}

api/advanced-topics/extension-host.md

@@ -0,0 +1,24 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: 106AA11C-DB26-493A-9E3C-16F513B2AEC8
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: The Visual Studio Code Extension Host is responsible for managing extensions and ensuring the stability and performance of Visual Studio Code.
+---
+
+# Extension Host
+
+As you learned in the [Extension Anatomy](/api/get-started/extension-anatomy) topic, an extension exposes the `activate` and `deactivate` methods and VS Code will manage its lifecycle. This topic provides more details on the **Extension Host** that manages all running extensions.
+
+**Extension host** is a Node.js process in VS Code responsible for loading and running extensions. Although you don't need to worry about the Extension Host when you are writing extensions, it is still useful to know what the Extension Host does to your extension.
+
+## Stability and Performance
+
+VS Code aims to deliver a stable and performant editor to end users, and misbehaving extensions should not impact the user experience. The Extension Host in VS Code prevents extensions from:
+
+- Impacting startup performance
+- Slowing down UI operations
+- Modifying the UI
+
+Additionally, VS Code lets extensions declare its [Activation Events](/api/references/activation-events) and loads them lazily. For example, the Markdown extension should only be loaded when a user opens a Markdown file. This makes sure that extensions do not consume unnecessary CPU and memory.

api/advanced-topics/using-proposed-api.md

@@ -0,0 +1,22 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: f4d4e9e0-8901-405c-aaf5-faa16c32588b
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: Use Visual Studio Code's Proposed API
+---
+
+# Using Proposed API
+
+At Visual Studio Code, we take Extension API compatibility seriously. We give our best effort to avoid breaking API changes, and extension authors could expect published extensions to continue to work. However, this puts great limitation on us: once we introduce an API, we cannot easily change it any more.
+
+Proposed API solves the problem for us. Proposed API is a set of unstable API that are implemented in VS Code but not exposed to the public as stable API does. They are **subject to change**, **only available in Insider distribution** and **cannot be used in published extensions**. Nevertheless, extension authors could test these new API in local development and provide feedback for VS Code team to iterate on the API. Eventually, Proposed API finds their way into the stable API and becomes available for general use.
+
+## Using Proposed API
+
+These are the steps for testing Proposed API in local extension development:
+
+- Use [Insiders](/insiders) release of VS Code.
+- Add `"enableProposedApi": true` to your `package.json`.
+- Copy the latest version of the [`vscode.proposed.d.ts`](https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.proposed.d.ts) into your project.

api/extension-capabilities/common-capabilities.md

@@ -0,0 +1,78 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: 9c48dfbf-e49d-4f33-aadc-5ebf06d5dde0
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: Common capabilities that Visual Studio Code extensions (plug-ins) can take advantage of
+---
+
+# Common Capabilities
+
+Common Capabilities are important building blocks for your extensions. Almost all extensions use some of these functionalities. Here is how you can take advantage of them.
+
+## Command
+
+Command is central to how VS Code works. You open the Command Palette to execute commands, bind custom keybindings to commands, and right-click to invoke commands in Context Menus.
+
+An extension could:
+
+- Register and execute commands with the [`vscode.commands`](/api/references/vscode-api#commands) API.
+- Make commands available in the Command Palette with the [`contributes.commands`](/api/references/contribution-points#contributes.commands) Contribution Point.
+
+Learn more about commands at the [Extension Guides / Command](/api/extension-guides/command) topic.
+
+## Configuration
+
+An extension can contribute extension-specific settings with the [`contributes.configuration`](/api/references/contribution-points#contributes.configuration) Contribution Point and read them using the [`workspace.getConfiguration`](/api/references/vscode-api#workspace.getConfiguration) API.
+
+## Keybinding
+
+An extension can add custom keybindings. Read more in the [`contributes.keybindings`](/api/references/contribution-points#contributes.keybindings) and [Key Bindings](/docs/getstarted/keybindings) topics.
+
+## Context Menu
+
+An extension can register custom Context Menu items that will be displayed in different parts of the VS Code UI on right-click. Read more at the [`contributes.menus`](/api/references/contribution-points#contributes.menus) Contribution Point.
+
+## Data Storage
+
+There are three options for storing data:
+
+- [`ExtensionContext.workspaceState`](/api/references/vscode-api#ExtensionContext.workspaceState): A workspace storage where you can write key/value pairs. VS Code manages the storage and will restore it when the same workspace is opened again.
+- [`ExtensionContext.globalState`](/api/references/vscode-api#ExtensionContext.globalState): A global storage where you can write key/value pairs. VS Code manages the storage and will restore it for each extension activation.
+- [`ExtensionContext.storagePath`](/api/references/vscode-api#ExtensionContext.storagePath): A workspace specific storage path pointing to a local directory where your extension has write/read access. This is a good option if you need to store large files that is accessible only from current workspace.
+- [`ExtensionContext.globalStoragePath`](/api/references/vscode-api#ExtensionContext.globalStoragePath): A global storage path pointing to a local directory where your extension has write/read access. This is a good option if you need to store large files that is accessible from all workspaces.
+
+The extension context is available to the `activate` function in the [Extension Entry File](/api/get-started/extension-anatomy#extension-entry-file).
+
+## Display Notifications
+
+Almost all extensions need to present information to the user at some point. VS Code offers three APIs for displaying notification messages of different severity:
+
+- [`window.showInformationMessage`](/api/references/vscode-api#window.showInformationMessage)
+- [`window.showWarningMessage`](/api/references/vscode-api#window.showWarningMessage)
+- [`window.showErrorMessage`](/api/references/vscode-api#window.showErrorMessage)
+
+## Quick Pick
+
+With the [`vscode.QuickPick`](/api/references/vscode-api#QuickPick) API, you can easily collect user input or let the user make a selection from multiple options. The [QuickInput Sample](https://github.com/Microsoft/vscode-extension-samples/tree/master/quickinput-sample) illustrates the API.
+
+## File Picker
+
+Extensions can use the [`vscode.window.showOpenDialog`](/api/references/vscode-api#vscode.window.showOpenDialog) API to open the system file picker and select files or folders.
+
+## Output Channel
+
+The Output Panel displays a collection of [`OutputChannel`](/api/references/vscode-api#OutputChannel), which are great for logging purpose. You can easily take advantage of it with the [`window.createOutputChannel`](/api/references/vscode-api#window.createOutputChannel) API.
+
+## Progress API
+
+You can use the [`vscode.Progress`](/api/references/vscode-api#Progress) API for reporting progress updates to the user.
+
+Progress can be shown in different locations using the [`ProgressLocation`](/api/references/vscode-api#ProgressLocation) option:
+
+- In the Notifications area
+- In the Source Control view
+- General progress in the VS Code window
+
+The [Progress Sample](https://github.com/Microsoft/vscode-extension-samples/tree/master/progress-sample) illustrates this API.

api/extension-capabilities/extending-core-functionalities.md

@@ -0,0 +1,12 @@
+---
+DateApproved:
+MetaDescription:
+---
+
+# Extending Core Functionalities
+
+Talk about the core functionalities that extension could plug-in their providers for:
+
+- File System Provider
+- Search Provider
+- SCM Provider

api/extension-capabilities/extending-workbench.md

@@ -0,0 +1,49 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: e0d5bd37-f020-4235-ad81-c977baaeb24f
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: Explain how to extend Visual Studio Code's workbench area with custom UI components
+---
+
+# Extending Workbench
+
+"Workbench" refers to the overall Visual Studio Code UI that encompasses the following UI components:
+
+- Title Bar
+- Activity Bar
+- Side Bar
+- Panel
+- Editor Group
+- Status Bar
+
+VS Code provides various APIs that allow you to add your own components to the Workbench. For example, in the image below:
+
+![workbench-contribution](images/extending-workbench/workbench-contribution.png)
+
+- Activity Bar: The [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice) adds a [View Container](#view-container)
+- Side Bar: The built-in [NPM extension](https://github.com/Microsoft/vscode/tree/master/extensions/npm) adds a [Tree View](#tree-view) to the Explorer View
+- Editor Group: The built-in [Markdown extension](https://github.com/Microsoft/vscode/tree/master/extensions/markdown-language-features) adds a [Webview](#webview) next to other editors in the Editor Group
+- Status Bar: The [VSCodeVim extension](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim) adds a [Status Bar Item](#status-bar-item) in the Status Bar
+
+## Views Container
+
+With the [`contributes.viewsContainers`](/api/references/contribution-points#contributes.viewsContainers) Contribution Point, you can add new Views Containers that display next to the five built-in Views Containers. Learn more at the [Tree View](/api/extension-guides/tree-view) topic.
+
+## Tree View
+
+With the [`contributes.views`](/api/references/contribution-points#contributes.views) Contribution Point, you can add new Views that display in any of the View Containers. Learn more at the [Tree View](/api/extension-guides/tree-view) topic.
+
+## Webview
+
+Webviews are highly customizable views built with HTML/CSS/JavaScript. They display next to text editors in the Editor Group areas. Read more about Webview in the [Webview Guide](/api/extension-guides/webview).
+
+## Status Bar Item
+
+Extensions can create custom [`StatusBarItem`](/api/references/vscode-api#StatusBarItem) that display in the Status Bar. Status Bar Items can show text and icons and run commands on click events.
+
+- Show text and icons
+- Run a command on click
+
+A Status Bar extension sample can be found [here](https://github.com/Microsoft/vscode-extension-samples/tree/master/statusbar-sample).

api/extension-capabilities/overview.md

@@ -0,0 +1,121 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: d22675fc-6609-43f2-a66b-8f2a52597195
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: Learn the details of what's possible with Visual Studio Code's rich extension (plug-in) API.
+---
+
+# Extensions Capabilities Overview
+
+Visual Studio Code offers many ways for extensions to extend its capabilities. It can sometimes be hard to find the right [Contribution Points](/api/references/contribution-points) and [VS Code API](/api/references/vscode-api) to use. This topic splits extension capabilities into a few categories. Each category describes:
+
+- Some functionalities your extension could use
+- Links to more detailed topics for using these functionalities
+- A few extension ideas
+
+However, we also impose [restrictions](#restrictions) upon extensions to ensure the stability and performance of VS Code. For example, extensions cannot access the DOM of VS Code UI.
+
+## Common Capabilities
+
+[Common Capabilities](./common-capabilities) are core pieces of functionality that you can use in any extension.
+
+Some of these capabilities include:
+
+- Registering commands, configurations, keybindings, or context menu items.
+- Storing workspace or global data.
+- Displaying notification messages.
+- Using Quick Pick to collect user input.
+- Open the system file picker to let users select files or folders.
+- Use the Progress API to indicate long-running operations.
+
+## Theming
+
+[Theming](./theming) controls the look of VS Code, both the colors of source code in the editor and the colors of the VS Code UI. If you've ever wanted to make it look like you're coding the Matrix by making VS Code different shades of green, or just wanted to create the ultimate, minimalist grayscale workspace, then themes are for you.
+
+**Extension Ideas**
+
+- Change colors of your source code.
+- Change colors of the VS Code UI.
+- Port an existing TextMate theme to VS Code.
+- Add custom file icons.
+
+## Declarative Language Features
+
+[Declarative Language Features](/api/language-extensions/overview#declarative-language-features) adds basic text editing support for a programming language such as bracket matching, auto-indentation and syntax highlighting. This is done declaratively, without writing any code. For more advanced language features, like IntelliSense or debugging, see [Programmatic Language Features](#programmatic-language-features).
+
+**Extension Ideas**
+
+- Bundle common JavaScript snippets into an extension.
+- Tell VS Code about a new programming language.
+- Add or replace the grammar for a programming language.
+- Extend an existing grammar with grammar injections.
+- Port an existing TextMate grammar to VS Code.
+
+## Programmatic Language Features
+
+[Programmatic Language Features](/api/language-extensions/overview#programmatic-language-features) add rich programming language support such as Hovers, Go to Definition, diagnostic errors, IntelliSense and CodeLens. These language features are exposed through the [`vscode.languages.*`](/api/references/vscode-api#languages) API. An extension can either use these API directly, or write a Language Server and adapt it to VS Code using the VS Code [Language Server library](https://github.com/Microsoft/vscode-languageserver-node).
+
+Although we provide a listing of [language features](/api/language-extensions/programmatic-language-features) and their intended usage, nothing prevents you from using these API creatively. For example, CodeLens and Hovers are a great way to present additional information inline, while diagnostic errors can be used to highlight spelling or code style errors.
+
+**Extension Ideas**
+
+- Add hovers that show sample usage of an API.
+- Report spelling or linter errors in source code using diagnostics.
+- Register a new code formatter for HTML.
+- Provide rich, context-aware IntelliSense.
+- Add folding, breadcrumbs and outline support for a language.
+
+## Workbench Extensions
+
+[Workbench Extensions](./extending-workbench) extend the VS Code Workbench UI. Add new right-click actions to the File Explorer, or even build a custom explorer using VS Code's [TreeView](/api/extension-guides/tree-view) API. And if your extension needs a fully customized user interface, use the [Webview API](/api/extension-guides/webview) to build your own document preview or UI using standard HTML, CSS, and JavaScript.
+
+**Extension Ideas**
+
+- Add custom context menu actions to the File Explorer.
+- Create a new, interactive TreeView in the Side Bar.
+- Define a new Activity Bar view.
+- Show new information in the Status Bar.
+- Render custom content using the `WebView` API.
+- Contribute Source Control providers.
+
+## Debugging
+
+You can take advantage of VS Code's [Debugging](/docs/editor/debugging) functionality by writing [Debugger Extensions](/api/extension-guides/debugger-extension) that connect VS Code's debugging UI to a specific debugger or runtime.
+
+**Extension Ideas**
+
+- Connect VS Code's debugging UI to a debugger or runtime by contributing a [Debug Adapter implementation](https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/).
+- Specify the languages supported by a debugger extension.
+- Provide rich IntelliSense and hover information for the debug configuration attributes used by the debugger.
+- Provide debug configuration snippets.
+
+On the other hand, VS Code also offers a set of [Debug Extension API](/api/references/vscode-api#debug), with which you can implement debug-related functionality on top of any VS Code debugger, in order to automate users' debugging experience.
+
+**Extension Ideas**
+
+- Start debug sessions based on dynamically created debug configurations.
+- Track the lifecycle of debug sessions.
+- Create and manage breakpoints programmatically.
+
+<!-- Add below content back after writing ./extending-core-functionalities.md  -->
+<!-- ## Core Extensions
+
+[Core Extensions](extending-core-functionalities) are for very advanced users. These let you build a custom back end for many of VS Code's low-level functionality. For example, the `FileSystem` API can be used to support working with files over FTP or other protocols. Core extensions typically work transparently from a user's point of view.
+
+**Extension Ideas**
+
+- Add support for working with remote files over FTP or SFTP.
+- Register new source control provider, such as Mercurial.
+- Implement a custom file search provider. -->
+
+## Restrictions
+
+There are certain restrictions we impose upon extensions. Here are the restrictions and their purposes.
+
+### No DOM Access
+
+Extensions have no access to the DOM of VS Code UI. You **cannot** write an extension that applies custom CSS to VS Code or adds a HTML element to VS Code UI.
+
+At VS Code, we're continually trying to optimize use of the underlying web technologies to deliver an always available, highly responsive editor and we will continue to tune our use of the DOM as these technologies and our product evolve. To ensure that extensions cannot interfere with the stability and performance of VS Code, and that we can continue to improve the DOM of VS Code without breaking existing extensions, we run extensions in an [Extension Host](/api/advanced-topics/extension-host) process and prevent direct access to the DOM.

api/extension-capabilities/theming.md

@@ -0,0 +1,37 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: 37b6ae0a-d1b5-48b6-9bd4-9b50ef11d573
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: Learn how to add custom themes for colors and icons in Visual Studio Code.
+---
+
+# Theming
+
+In Visual Studio Code, there are two types of themes:
+
+- **Color Theme**: A mapping from both UI Component Identifier and Text Token Identifier to colors. Color theme allows you to apply your favorite colors to both VS Code UI Components and the text in the editor.
+- **Icon Theme**: A mapping from file type / file name to images. The file icon is displayed across the VS Code UI in places such as File Explorer, Quick Open List, and Editor Tab.
+
+## Color Theme
+
+![color-theme](images/theming/color-theme.png)
+
+As you can see in the illustration, Color Theme defines two mappings:
+
+- The `colors` mapping that controls colors for UI Components.
+- The `tokenColors` mapping that controls colors for each source code token (your source code is broken into tokens by a [grammar](/api/language-extensions/syntax-highlight-guide)).
+
+We have a [Color Theme Guide](/api/extension-guides/color-theme) and a [Color Theme Sample](https://github.com/Microsoft/vscode-extension-samples/tree/master/theme-sample) that illustrates how to create a theme.
+
+## Icon Theme
+
+Icon themes allow you to:
+
+- Create a mapping from unique icon identifiers to images or font icons.
+- Associate files to these unique icon identifiers by filenames or file language types.
+
+The [Icon Theme Guide](/api/extension-guides/icon-theme) discusses how to create an Icon Theme.
+
+![icon-theme](images/theming/icon-theme.png)

api/extension-guides/color-theme.md

@@ -0,0 +1,116 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: 113b458a-3692-4ccf-a181-048bd572a120
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: A guide to creating Color Theme in Visual Studio Code
+---
+
+# Color Theme
+
+Colors visible in the Visual Studio Code user interface fall in two categories:
+
+- Workbench colors used in views and editors, from the Activity Bar to the Status Bar. A complete list of all these colors can be found in the [theme color reference](/api/references/theme-color).
+- Syntax colors used for source code in the editor. The theming of these colors is different as syntax colorization is based on TextMate grammars and TextMate themes.
+
+This guide will cover the different ways in which you can create themes.
+
+## Workbench colors
+
+The easiest way to create a new workbench color theme is to start with an existing color theme and customize it. First switch to the color theme that you want to modify, then open your [settings](/docs/getstarted/settings) and make changes to the `workbench.colorCustomizations` setting. Changes are applied live to your VS Code instance.
+
+The following, for example, would change the color of the title bar:
+
+```json
+{
+  "workbench.colorCustomizations": {
+    "titleBar.activeBackground": "#ff0000"
+  }
+}
+```
+
+A complete list of all themable colors can be found in the [color reference](/api/references/theme-color).
+
+## Syntax colors
+
+For syntax highlighting colors, there are two approaches. You just simply reference an existing TextMate theme (`.tmTheme` file) from the community, or you can come up with your own theming rules. The easiest way is to start with an existing theme and customize it, much like in the workbench colors section above.
+
+First switch to the color theme to customize and use the `editor.tokenColorCustomizations` [settings](/docs/getstarted/settings). Changes are applied live to your VS Code instance and no refreshing or reloading is necessary.
+
+For example, the following would change the color of comments within the editor:
+
+```json
+{
+  "editor.tokenColorCustomizations": {
+    "comments": "#FF0000"
+  }
+}
+```
+
+The setting supports a simple model with a set of common token types such as 'comments', 'strings' and 'numbers' available. If you want to color more than that, you need to use TextMate theme rules directly, which are explained in detail in the [Syntax Highlighting Guide](/api/language-extensions/syntax-highlight-guide).
+
+## Create a new Color Theme
+
+Once you have tweaked your theme colors using `workbench.colorCustomizations` and `editor.tokenColorCustomizations`, it's time to create the actual theme.
+
+1. Generate a theme file using the **Developer: Generate Color Theme from Current Settings** command from the **Command Palette**
+2. Use VS Code's [Yeoman](http://yeoman.io) extension generator to generate a new theme extension:
+
+   ```bash
+   npm install -g yo generator-code
+   yo code
+   ```
+
+3. If you customized a theme as described above, select 'Start fresh'.
+
+   ![yo code theme](./images/color-theme/yocode-colortheme.png)
+
+4. Copy the theme file generated from your settings to the new extension.
+
+You can also use an existing TextMate theme by telling the extension generator to import a TextMate theme file (.tmTheme) and package it for use in VS Code. Alternatively, if you have already downloaded the theme, replace the `tokenColors` section with a link to the `.tmTheme` file to use.
+
+```json
+{
+  "type": "dark",
+  "colors": {
+    "editor.background": "#1e1e1e",
+    "editor.foreground": "#d4d4d4",
+    "editorIndentGuide.background": "#404040",
+    "editorRuler.foreground": "#333333",
+    "activityBarBadge.background": "#007acc",
+    "sideBarTitle.foreground": "#bbbbbb"
+  },
+  "tokenColors": "./Diner.tmTheme"
+}
+```
+
+> **Tip:** Give your color definition file the `.color-theme.json` suffix and you will get hovers, code completion, color decorators, and color pickers when editing.
+
+> **Tip:** [ColorSublime](https://colorsublime.github.io) has hundreds of existing TextMate themes to choose from. Pick a theme you like and copy the Download link to use in the Yeoman generator or into your extension. It will be in a format like `"https://raw.githubusercontent.com/Colorsublime/Colorsublime-Themes/master/themes/(name).tmTheme"`
+
+## Test a new Color Theme
+
+To try out the new theme, press F5 to launch an Extension Development Host window.
+
+There, open the Color Theme picker with **File** > **Preferences** > **Color Theme** and you can see your theme in the drop-down list. Arrow up and down to see a live preview of your theme.
+
+![select my theme](images/color-theme/mytheme.png)
+
+Changes to the theme file are applied live in the `Extension Development Host` window.
+
+## Publishing a Theme to the Extension Marketplace
+
+If you'd like to share your new theme with the community, you can publish it to the [Extension Marketplace](/docs/editor/extension-gallery). Use the [vsce publishing tool](/api/working-with-extensions/publishing-extension) to package your theme and publish it to the VS Code Marketplace.
+
+> **Tip:** To make it easy for users to find your theme, include the word "theme" in the extension description and set the `Category` to `Theme` in your `package.json`.
+
+We also have recommendations on how to make your extension look great on the VS Code Marketplace, see [Marketplace Presentation Tips](/api/references/extension-manifest#marketplace-presentation-tips).
+
+## Adding a new Color Id
+
+Color ids can also be contributed by extensions through the [color contribution point](/api/references/contribution-points#contributes.colors). These colors also appear when using code complete in the `workbench.colorCustomizations` settings and the color theme definition file. Users can see what colors an extension defines in the [extension contributions](/docs/editor/extension-gallery#_extension-details) tab.
+
+## Further reading
+
+- [CSS Tricks - Creating a VS Code theme](https://css-tricks.com/creating-a-vs-code-theme/)

api/extension-guides/command.md

@@ -0,0 +1,201 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: 995c7085-5fc0-44e0-a171-30a759c0b7da
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: A guide to using commands programmatically in Visual Studio Code extensions (plug-ins)
+---
+
+# Commands
+
+Commands trigger actions in Visual Studio Code. If you have ever [configured a keybinding](/docs/getstarted/keybindings), then you've worked with commands. Commands are also used by extensions to expose functionality to users, bind to actions in VS Code's UI, and implement internal logic.
+
+## Using Commands
+
+VS Code includes a large set of [built-in commands](/api/references/commands) that you can use to interact with the editor, control the user interface, or perform background operations. Many extensions also expose their core functionality as commands that users and other extensions can leverage.
+
+### Programmatically executing a command
+
+The [`vscode.commands.executeCommand`](/api/references/vscode-api#commands.executeCommand) API programmatically executes a command. This lets you leverage VS Code's built-in functionality, and build on extensions such as VS Code's built-in Git and Markdown extensions.
+
+The `editor.action.addCommentLine` command, for example, comments the currently selected lines in the active text editor:
+
+```ts
+import * as vscode from 'vscode';
+
+function commentLine() {
+  vscode.commands.executeCommand('editor.action.addCommentLine');
+}
+```
+
+Some commands take arguments that control their behavior. Commands may also return a result. The API-like `vscode.executeDefinitionProvider` command, for example, queries a document for definitions at a given position. It takes a document URI and a position as arguments, and returns a promise with a list of definitions:
+
+```ts
+import * as vscode from 'vscode';
+
+async function printDefinitionsForActiveEditor() {
+  const activeEditor = vscode.window.activeTextEditor;
+  if (!activeEditor) {
+    return;
+  }
+
+  const definitions = await vscode.commands.executeCommand<vscode.Location[]>(
+    'vscode.executeDefinitionProvider',
+    activeEditor.document.uri,
+    activeEditor.selection.active
+  );
+
+  for (const definition of definitions) {
+    console.log(definition);
+  }
+}
+```
+
+To find available commands:
+
+- [Browse the keyboard shortcuts](/docs/getstarted/keybindings)
+- [Look through VS Code's built-in advanced commands api](/api/references/commands)
+
+### Command URIs
+
+Commands URIs are links that execute a given command. They can be used as clickable links in hover text, completion item details, or inside of webviews.
+
+A command URI uses the `command` scheme followed by the command name. The command URI for the `editor.action.addCommentLine` command, for example, is `command:editor.action.addCommentLine`. Here's a hover provider that shows a link in the comments of the current line in the active text editor:
+
+```ts
+import * as vscode from 'vscode';
+
+export function activate(context: vscode.ExtensionContext) {
+  vscode.languages.registerHoverProvider(
+    'javascript',
+    new class implements vscode.HoverProvider {
+      provideHover(
+        _document: vscode.TextDocument,
+        _position: vscode.Position,
+        _token: vscode.CancellationToken
+      ): vscode.ProviderResult<vscode.Hover> {
+        const commentCommandUri = vscode.Uri.parse(`command:editor.action.addCommentLine`);
+        const contents = new vscode.MarkdownString(`[Add comment](${commentCommandUri})`);
+
+        // To enable command URIs in Markdown content, you must set the `isTrusted` flag.
+        // When creating trusted Markdown string, make sure to properly sanitize all the
+        // input content so that only expected command URIs can be executed
+        contents.isTrusted = true;
+
+        return new vscode.Hover(contents);
+      }
+    }()
+  );
+}
+```
+
+The list of arguments to the command is passed as a JSON array that has been properly URI encoded: The example below uses the `git.stage` command to create a hover like that stages the current file:
+
+```ts
+import * as vscode from 'vscode';
+
+export function activate(context: vscode.ExtensionContext) {
+  vscode.languages.registerHoverProvider(
+    'javascript',
+    new class implements vscode.HoverProvider {
+      provideHover(
+        document: vscode.TextDocument,
+        _position: vscode.Position,
+        _token: vscode.CancellationToken
+      ): vscode.ProviderResult<vscode.Hover> {
+        const args = [{ resourceUri: document.uri }];
+        const stageCommandUri = vscode.Uri.parse(
+          `command:git.stage?${encodeURIComponent(JSON.stringify(args))}`
+        );
+        const contents = new vscode.MarkdownString(`[Stage file](${stageCommandUri})`);
+        contents.isTrusted = true;
+        return new vscode.Hover(contents);
+      }
+    }()
+  );
+}
+```
+
+## Creating new commands
+
+### Registering a command
+
+[`vscode.commands.registerCommand`](/api/references/vscode-api#commands.registerCommand) binds a command id to a handler function in your extension:
+
+```ts
+import * as vscode from 'vscode';
+
+export function activate(context: vscode.ExtensionContext) {
+  const command = 'myExtension.sayHello';
+
+  const commandHandler = (name?: string = 'world') => {
+    console.log(`Hello ${name}!!!`);
+  };
+
+  context.subscriptions.push(vscode.commands.registerCommand(command, commandHandler));
+}
+```
+
+The handler function will be invoked whenever the `myExtension.sayHello` command is executed, be it programmatically with `executeCommand`, from the VS Code UI, or through a keybinding.
+
+### Creating a user facing command
+
+`vscode.commands.registerCommand` only binds a command id to a handler function. To expose this command in the Command Palette so it is discoverable by users, you also need a corresponding command `contribution` in your extension's `package.json`:
+
+```json
+{
+  "contributes": {
+    "commands": [
+      {
+        "command": "myExtension.sayHello",
+        "title": "Say Hello"
+      }
+    ]
+  }
+}
+```
+
+The `commands` contribution tells VS Code that your extension provides a given command, and also lets you control how the command is displayed in the UI. Now our command will show up in the Command Palette:
+
+![The contributed command in the Command Palette](images/commands/palette.png)
+
+We still need to call `registerCommand` to actually tie the command id to the handler. This means that if the user selects the `myExtension.sayHello` command from the Command Palette but our extension has not been activated yet, nothing will happen. To prevent this, extensions must register an `onCommand` `activiationEvent` for all user facing commands:
+
+```json
+{
+  "activationEvents": ["onCommand:myExtension.sayHello"]
+}
+```
+
+Now when a user first invokes the `myExtension.sayHello` command from the Command Palette or through a keybinding, the extension will be activated and `registerCommand` will bind `myExtension.sayHello` to the proper handler.
+
+You do not need an `onCommand` activation event for internal commands but you must define them for any commands that:
+
+- Can be invoked using the Command Palette.
+- Can be invoked using a keybinding.
+- Can be invoked through the VS Code UI, such as through the editor title bar.
+- Is intended as an API for other extensions to consume.
+
+### Controlling when a command shows up in the Command Palette
+
+By default, all user facing commands contributed through the `commands` section of the `package.json` show up in the Command Palette. However, many commands are only relevant in certain circumstances, such as when there is an active text editor of a given language or when the user has a certain configuration option set.
+
+The [`menus.commandPalette`](/api/references/contribution-points#contributes.menus) contribution point lets you restrict when a command should show in the Command Palette. It takes the id of the target command and a [when clause](/docs/getstarted/keybindings#_when-clause-contexts) that controls when the command is shown:
+
+```json
+{
+  "contributes": {
+    "menus": {
+      "commandPalette": [
+        {
+          "command": "myExtension.sayHello",
+          "when": "editorLangId == markdown"
+        }
+      ]
+    }
+  }
+}
+```
+
+Now the `myExtension.sayHello` command will only show up in the Command Palette when the user is in a Markdown file.

api/extension-guides/debugger-extension.md

@@ -0,0 +1,367 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: 49EF49AD-8BE6-4D46-ADC8-D678BDC04E85
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: Learn how to provide debugger extensions (plug-ins) for Visual Studio Code through a Debug Adapter.
+---
+
+# Debugger Extension
+
+Visual Studio Code's debugging architecture allows extension authors to easily integrate existing debuggers into VS Code, while having a common user interface with all of them.
+
+VS Code ships with one built-in debugger extension, the [Node.js](https://nodejs.org) debugger extension, which is an excellent showcase for the many debugger features supported by VS Code:
+
+![VS Code Debug Features](images/debugger-extension/debug-features.png)
+
+This screenshot shows the following debugging features:
+
+1. Debug configuration management.
+2. Debug actions for starting/stopping and stepping.
+3. Source-, function-, conditional-, inline breakpoints, and log points.
+4. Stack traces, including multi-thread and multi-process support.
+5. Navigating through complex data structures in views and hovers.
+6. Variable values shown in hovers or inlined in the source.
+7. Managing watch expressions.
+8. Debug console for interactive evaluation with autocomplete.
+
+This documentation will help you create a debugger extension which can make any debugger work with VS Code.
+
+## Debugging Architecture of VS Code
+
+VS Code implements a generic (language-agnostic) debugger UI based on an abstract protocol that we've introduced to communicate with debugger backends.
+Because debuggers typically do not implement this protocol, some intermediary is needed to "adapt" the debugger to the protocol.
+This intermediary is typically a standalone process that communicates with the debugger.
+
+![VS Code Debug Architecture](images/debugger-extension/debug-arch1.png)
+
+We call this intermediary the **Debug Adapter** (or **DA** for short) and the abstract protocol that is used between the DA and VS Code is the **Debug Adapter Protocol** (**DAP** for short).
+Since the Debug Adapter Protocol is independent from VS Code, it has its own [web site](https://microsoft.github.io/debug-adapter-protocol/) where you can find an [introduction and overview](https://microsoft.github.io/debug-adapter-protocol/overview), the detailed [specification](https://microsoft.github.io/debug-adapter-protocol/specification), and some lists with [known implementations and supporting tools](https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/).
+The history of and motivation behind DAP is explained in this [blog post](https://code.visualstudio.com/blogs/2018/08/07/debug-adapter-protocol-website#_why-the-need-for-decoupling-with-protocols).
+
+Since debug adapters are independent from VS Code and can be used in [other developments tools](https://microsoft.github.io/debug-adapter-protocol/implementors/tools/), they do not match VS Code's extensibility architecture which is based on extensions and contribution points.
+
+For this reason VS Code provides a contribution point, `debuggers`, where a debug adapter can be contributed under a specific debug type (e.g. `node` for the Node.js debugger). VS Code launches the registered DA whenever the user starts a debug session of that type.
+
+So in its most minimal form, a debugger extension is just a declarative contribution of a debug adapter implementation and the extension is basically a packaging container for the debug adapter without any additional code.
+
+![VS Code Debug Architecture 2](images/debugger-extension/debug-arch2.png)
+
+A more realistic debugger extension contributes many or all of the following declarative items to VS Code:
+
+- List of languages supported by the debugger. VS Code enables the UI to set breakpoints for those languages.
+- JSON schema for the debug configuration attributes introduced by the debugger. VS Code uses this schema to verify the configuration in the launch.json editor and provides IntelliSense.
+- Default debug configurations for the initial launch.json created by VS Code.
+- Debug configuration snippets that a user can add to a launch.json file.
+- Declaration of variables that can be used in debug configurations.
+
+You can find more information in [`contributes.breakpoints`](/api/references/contribution-points#contributes.breakpoints) and [`contributes.debuggers`](/api/references/contribution-points#contributes.debuggers) references.
+
+In addition to the purely declarative contributions from above, the Debug Extension API enables this code-based functionality:
+
+- Dynamically generated default debug configurations for the initial launch.json created by VS Code.
+- Determine the debug adapter to use dynamically.
+- Verify or modify debug configurations before they are passed to the debug adapter.
+- Communicate with the debug adapter.
+- Send messages to the debug console.
+
+In the rest of this document we show how to develop a debugger extension.
+
+## The Mock Debug Extension
+
+Since creating a debug adapter from scratch is a bit heavy for this tutorial, we will start with a simple DA which we have created as an educational "debug adapter starter kit". It is called _Mock Debug_ because it does not talk to a real debugger, but mocks one. Mock Debug simulates a debugger and supports step, continue, breakpoints, exceptions, and variable access, but it is not connected to any real debugger.
+
+Before delving into the development setup for mock-debug, let's first install a [pre-built version](https://marketplace.visualstudio.com/items/andreweinand.mock-debug)
+from the VS Code Marketplace and play with it:
+
+- Switch to the Extensions viewlet and type "mock" to search for the Mock Debug extension,
+- "Install" and "Reload" the extension.
+
+To try Mock Debug:
+
+- Create a new empty folder `mock test` and open it in VS Code.
+- Create a file `readme.md` and enter several lines of arbitrary text.
+- Switch to the Debug view and press the gear icon.
+- VS Code will let you select an "environment" in order to create a default launch configuration. Pick "Mock Debug".
+- Press the green Start button and then Enter to confirm the suggested file `readme.md`.
+
+A debug session starts and you can "step" through the readme file, set and hit breakpoints, and run into exceptions (if the word `exception` appears in a line).
+
+![Mock Debugger running](images/debugger-extension/mock-debug.gif)
+
+Before using Mock Debug as a starting point for your own development, we recommend to uninstall the pre-built version first:
+
+- Switch to the Extensions viewlet and click on the gear icon of the Mock Debug extension.
+- Run the "Uninstall" action and then "Reload" the window.
+
+## Development Setup for Mock Debug
+
+Now let's get the source for Mock Debug and start development on it within VS Code:
+
+```bash
+git clone https://github.com/Microsoft/vscode-mock-debug.git
+cd vscode-mock-debug
+npm install
+```
+
+Open the project folder `vscode-mock-debug` in VS Code.
+
+What's in the package?
+
+- `package.json` is the manifest for the mock-debug extension:
+  - It lists the contributions of the mock-debug extension.
+  - The `compile` and `watch` scripts are used to transpile the TypeScript source into the `out` folder and watch for subsequent source modifications.
+  - The dependencies `vscode-debugprotocol`, `vscode-debugadapter`, and `vscode-debugadapter-testsupport` are NPM modules that simplify the development of node-based debug adapters.
+- `src/mockRuntime.ts` is a _mock_ runtime with a simple debug API.
+- The code that _adapts_ the runtime to the Debug Adapter Protocol lives in `src/mockDebug.ts`. Here you find the handlers for the various requests of the DAP.
+- Since the implementation of debugger extension lives in the debug adapter, there is no need to have extension code at all (i.e. code that runs in the extension host process). However, Mock Debug has a small `src/extension.ts` because it illustrates what can be done in the extension code of a debugger extension.
+
+Now build and launch the Mock Debug extension by selecting the **Extension** launch configuration and hitting `F5`.
+Initially, this will do a full transpile of the TypeScript sources into the `out` folder.
+After the full build, a _watcher task_ is started that transpiles any changes you make.
+
+After transpiling the source, a new VS Code window labelled "[Extension Development Host]" appears with the Mock Debug extension now running in debug mode. From that window open your `mock test` project with the `readme.md` file, start a debug session with 'F5', and then step through it:
+
+![Debugging Extension and Server](images/debugger-extension/debug-mock-session.png)
+
+Since you are running the extension in debug mode, you could now set and hit breakpoints in `src/extension.ts` but as I've mentioned above, there is not much interesting code executing in the extension. The interesting code runs in the debug adapter which is a separate process.
+
+In order to debug the debug adapter itself, we have to run it in debug mode. This is most easily achieved by running the debug adapter in _server mode_ and configure VS Code to connect to it. In your VS Code vscode-mock-debug project select the launch configuration **Server** from the drop down menu and press the green start button.
+
+Since we already had an active debug session for the extension the VS Code debugger UI now enters _multi session_ mode which is indicated by seeing the names of the two debug sessions **Extension** and **Server** showing up in the CALL STACK view:
+
+![Debugging Extension and Server](images/debugger-extension/debugger-extension-server.png)
+
+Now we are able to debug both the extension and the DA simultaneously.
+A faster way to arrive here is by using the **Extension + Server** launch configuration which launches both sessions automatically.
+
+An alternative, even simpler approach for debugging the extension and the DA can be found [below](#alternative-approach-to-develop-a-debugger-extension).
+
+Set a breakpoint at the beginning of method `launchRequest(...)` in file `src/mockDebug.ts` and as a last step configure the mock debugger to connect to the DA server by adding a `debugServer` attribute for port `4711` to your mock test launch config:
+
+```json
+{
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "type": "mock",
+      "request": "launch",
+      "name": "mock test",
+      "program": "${workspaceFolder}/readme.md",
+      "stopOnEntry": true,
+      "debugServer": 4711
+    }
+  ]
+}
+```
+
+If you now launch this debug configuration, VS Code does not start the mock debug adapter as a separate process, but directly connects to local port 4711 of the already running server, and you should hit the breakpoint in `launchRequest`.
+
+With this setup, you can now easily edit, transpile, and debug Mock Debug.
+
+But now the real work begins: you will have to replace the mock implementation of the debug adapter in `src/mockDebug.ts` and `src/mockRuntime.ts` by some code that talks to a "real" debugger or runtime. This involves understanding and implementing the Debug Adapter Protocol. More details
+about this can be found [here](https://microsoft.github.io/debug-adapter-protocol/overview#How_it_works).
+
+## Anatomy of the package.json of a Debugger Extension
+
+Besides providing a debugger-specific implementation of the debug adapter a debugger extension needs a `package.json` that contributes to the various debug-related contributions points.
+
+So let's have a closer look at the `package.json` of Mock Debug.
+
+Like every VS Code extension, the `package.json` declares the fundamental properties **name**, **publisher**, and **version** of the extension. Use the **categories** field to make the extension easier to find in the VS Code Extension Marketplace.
+
+```json
+{
+  "name": "mock-debug",
+  "displayName": "Mock Debug",
+  "version": "0.24.0",
+  "publisher": "...",
+  "description": "Starter extension for developing debug adapters for VS Code.",
+  "author": {
+    "name": "...",
+    "email": "..."
+  },
+  "engines": {
+    "vscode": "^1.17.0",
+    "node": "^7.9.0"
+  },
+  "icon": "images/mock-debug-icon.png",
+  "categories": ["Debuggers"],
+
+  "contributes": {
+    "breakpoints": [{ "language": "markdown" }],
+    "debuggers": [
+      {
+        "type": "mock",
+        "label": "Mock Debug",
+
+        "program": "./out/mockDebug.js",
+        "runtime": "node",
+
+        "configurationAttributes": {
+          "launch": {
+            "required": ["program"],
+            "properties": {
+              "program": {
+                "type": "string",
+                "description": "Absolute path to a text file.",
+                "default": "${workspaceFolder}/${command:AskForProgramName}"
+              },
+              "stopOnEntry": {
+                "type": "boolean",
+                "description": "Automatically stop after launch.",
+                "default": true
+              }
+            }
+          }
+        },
+
+        "initialConfigurations": [
+          {
+            "type": "mock",
+            "request": "launch",
+            "name": "Ask for file name",
+            "program": "${workspaceFolder}/${command:AskForProgramName}",
+            "stopOnEntry": true
+          }
+        ],
+
+        "configurationSnippets": [
+          {
+            "label": "Mock Debug: Launch",
+            "description": "A new configuration for launching a mock debug program",
+            "body": {
+              "type": "mock",
+              "request": "launch",
+              "name": "${2:Launch Program}",
+              "program": "^\"\\${workspaceFolder}/${1:Program}\""
+            }
+          }
+        ],
+
+        "variables": {
+          "AskForProgramName": "extension.mock-debug.getProgramName"
+        }
+      }
+    ]
+  },
+
+  "activationEvents": ["onDebug", "onCommand:extension.mock-debug.getProgramName"]
+}
+```
+
+Now take a look at the **contributes** section which contains the contributions specific to debug extensions.
+
+First, we use the **breakpoints** contribution point to list the languages for which setting breakpoints will be enabled. Without this, it would not be possible to set breakpoints in Markdown files.
+
+Next is the **debuggers** section. Here, one debugger is introduced under a debug **type** `mock`. The user can reference this type in launch configurations. The optional attribute **label** can be used to give the debug type a nice name when showing it in the UI.
+
+Since the debug extension uses a debug adapter, a relative path to its code is given as the **program** attribute.
+In order to make the extension self-contained the application must live inside the extension folder. By convention, we keep this applications inside a folder named `out` or `bin`, but you are free to use a different name.
+
+Since VS Code runs on different platforms, we have to make sure that the DA program supports the different platforms as well. For this we have the following options:
+
+1. If the program is implemented in a platform independent way, e.g. as program that runs on a runtime that is available on all supported platforms, you can specify this runtime via the **runtime** attribute. As of today, VS Code supports `node` and `mono` runtimes. Our Mock debug adapter from above uses this approach.
+
+1. If your DA implementation needs different executables on different platforms, the **program** attribute can be qualified for specific platforms like this:
+
+   ```json
+   "debuggers": [{
+       "type": "gdb",
+       "windows": {
+           "program": "./bin/gdbDebug.exe",
+       },
+       "osx": {
+           "program": "./bin/gdbDebug.sh",
+       },
+       "linux": {
+           "program": "./bin/gdbDebug.sh",
+       }
+   }]
+   ```
+
+1. A combination of both approaches is possible too. The following example is from the Mono DA which is implemented as a mono application that needs a runtime on macOS and Linux but not on Windows:
+
+   ```json
+   "debuggers": [{
+       "type": "mono",
+       "program": "./bin/monoDebug.exe",
+       "osx": {
+           "runtime": "mono"
+       },
+       "linux": {
+           "runtime": "mono"
+       }
+   }]
+   ```
+
+**configurationAttributes** declares the schema for the `launch.json` attributes that are available for this debugger. This schema is used for validating the `launch.json` and supporting IntelliSense and hover help when editing the launch configuration.
+
+The **initialConfigurations** define the initial content of the default `launch.json` for this debugger. This information is used when a project does not have a `launch.json` and a user starts a debug session or clicks on the gear icon in the debug viewlet. In this case VS Code lets the user pick a debug environment and then creates the corresponding `launch.json`:
+
+![Debugger Quickpick](images/debugger-extension/debug-init-config.png)
+
+Instead of defining the initial content of the `launch.json` statically in the `package.json`, it is possible to compute the initial configurations dynamically by implementing a `DebugConfigurationProvider` (for details see the section [Using a DebugConfigurationProvider below](#using-a-debugconfigurationprovider)).
+
+**configurationSnippets** define launch configuration snippets that get surfaced in IntelliSense when editing the `launch.json`. As a convention, prefix the `label` attribute of a snippet by the debug environment name so that it can be clearly identified when presented in a list of many snippet proposals.
+
+The **variables** contribution binds "variables" to "commands". These variables can be used in the launch configuration using the **\${command:xyz}** syntax and the variables are substituted by the value returned from the bound command when a debug session is started.
+
+The implementation of a command lives in the extension and it can range from a simple expression with no UI, to sophisticated functionality based on the UI features available in the extension API.
+Mock Debug binds a variable `AskForProgramName` to the command `extension.mock-debug.getProgramName`. The [implementation](https://github.com/Microsoft/vscode-mock-debug/blob/606454ff3bd669867a38d9b2dc7b348d324a3f6b/src/extension.ts#L21-L26) of this command in `src/extension.ts` uses the `showInputBox` to let the user enter a program name:
+
+```ts
+vscode.commands.registerCommand('extension.mock-debug.getProgramName', config => {
+  return vscode.window.showInputBox({
+    placeHolder: 'Please enter the name of a markdown file in the workspace folder',
+    value: 'readme.md'
+  });
+});
+```
+
+The variable can now be used in any string typed value of a launch configuration as **\${command:AskForProgramName}**.
+
+## Using a DebugConfigurationProvider
+
+If the static nature of debug contributions in the `package.json` is not sufficient, a `DebugConfigurationProvider` can be used to dynamically control the following aspects of a debug extension:
+
+- The initial debug configurations for a newly created launch.json can be generated dynamically, e.g. based on some contextual information available in the workspace.
+- A launch configuration can be _resolved_ (or modified) before it is used to start a new debug session. This allows for filling in default values based on information available in the workspace.
+
+The `MockConfigurationProvider` in `src/extension.ts` implements `resolveDebugConfiguration` to detect the case where a debug session is started when no launch.json exists, but a Markdown file is open in the active editor. This is a typical scenario where the user has a file open in the editor and just wants to debug it without creating a launch.json.
+
+A debug configuration provider is registered for a specific debug type via `vscode.debug.registerDebugConfigurationProvider`, typically in the extension's `activate` function.
+To ensure that the `DebugConfigurationProvider` is registered early enough, the extension must be activated as soon as the debug functionality is used. This can be easily achieved by configuring extension activation for the `onDebug` event in the `package.json`:
+
+```json
+"activationEvents": [
+    "onDebug",
+    // ...
+],
+```
+
+This catch-all `onDebug` is triggered as soon as any debug functionality is used. This works fine as long as the extension has cheap startup costs (i.e. does not spend a lot of time in its startup sequence). If a debug extension has an expensive startup (for instance because of starting a language server), the `onDebug` activation event could negatively affect other debug extensions, because it is triggered rather early and does not take a specific debug type into account.
+
+A better approach for expensive debug extensions is to use more fine-grained activation events:
+
+- `onDebugInitialConfigurations` is fired just before the `provideDebugConfigurations` method of the `DebugConfigurationProvider` is called.
+- `onDebugResolve:type` is fired just before the `resolveDebugConfiguration` method of the `DebugConfigurationProvider` for the specified type is called.
+
+**Rule of thumb:** If activation of a debug extensions is cheap, use `onDebug`. If it is expensive, use `onDebugInitialConfigurations` and/or `onDebugResolve` depending on whether the `DebugConfigurationProvider` implements the corresponding methods `provideDebugConfigurations` and/or `resolveDebugConfiguration`.
+
+## Publishing your debugger extension
+
+Once you have created your debugger extension you can publish it to the Marketplace:
+
+- Update the attributes in the `package.json` to reflect the naming and purpose of your debugger extension.
+- Upload to the Marketplace as described in [Publishing Extension](/api/working-with-extensions/publishing-extension).
+
+## Alternative approach to develop a debugger extension
+
+As we have seen, developing a debugger extension typically involves debugging both the extension and the debug adapter in two parallel sessions. As explained above VS Code supports this nicely but development could be easier if both the extension and the debug adapter would be one program that could be debugged in one debug session.
+
+This approach is in fact easily doable as long as your debug adapter is implemented in TypeScript/JavaScript. The basic idea is to run the debug adapter as a server inside the extension host and to make VS Code to connect to it instead of launching a new debug adapter per session.
+
+Mock Debug shows how a [DebugAdapterDescriptorFactory](https://github.com/Microsoft/vscode-mock-debug/blob/6a2ef01b95bb22cdf55683f4d616cad501051510/src/extension.ts#L74-L98) can be used to create and [register](https://github.com/Microsoft/vscode-mock-debug/blob/6a2ef01b95bb22cdf55683f4d616cad501051510/src/extension.ts#L32-L36) a server-based debug adapter.
+The feature is enabled by setting the compile time flag [`EMBED_DEBUG_ADAPTER`](https://github.com/Microsoft/vscode-mock-debug/blob/6a2ef01b95bb22cdf55683f4d616cad501051510/src/extension.ts#L17) to true. If you now start debugging the extension with **F5** you will hit breakpoints not only in the extension host but in the debug adapter as well.

api/extension-guides/file-system-provider.md

@@ -0,0 +1,8 @@
+---
+DateApproved:
+MetaDescription:
+---
+
+# File System Provider
+
+For https://github.com/Microsoft/vscode-extension-samples/tree/master/fsprovider-sample and https://github.com/Microsoft/vscode-extension-samples/tree/master/nodefs-provider-sample

api/extension-guides/i18n.md

@@ -0,0 +1,8 @@
+---
+DateApproved:
+MetaDescription:
+---
+
+# Internationalization
+
+https://github.com/Microsoft/vscode-extension-samples/tree/master/i18n-sample

api/extension-guides/icon-theme.md

@@ -0,0 +1,160 @@
+---
+# DO NOT TOUCH — Managed by doc writer
+ContentId: f470466d-89b0-4115-ab7a-2448023b0a6d
+DateApproved: 3/7/2019
+
+# Summarize the whole topic in less than 300 characters for SEO purpose
+MetaDescription: A guide to creating Icon Theme in Visual Studio Code
+---
+
+# Icon Theme
+
+Visual Studio Code displays icons next to filenames throughout its UI, and extensions can contribute new sets of file icons that users can choose from.
+
+## Adding a new Icon Theme
+
+You can create your own icon theme from icons (preferably SVG) and from icon fonts. As example, check out the two built-in themes: [Minimal](https://github.com/Microsoft/vscode/tree/master/extensions/theme-defaults) and [Seti](https://github.com/Microsoft/vscode/tree/master/extensions/theme-seti).
+
+To begin, create a VS Code extension and add the `iconTheme` contribution point.
+
+```json
+{
+  "contributes": {
+    "iconThemes": [
+      {
+        "id": "turtles",
+        "label": "Turtles",
+        "path": "./fileicons/turtles-icon-theme.json"
+      }
+    ]
+  }
+}
+```
+
+The `id` is the identifier for the icon theme. It is currently only used internally. In the future, it might be used in the settings, so make it unique but also readable. `label` is shown in the icon theme picker drop-down. The `path` points to a file in the extension that defines the icon set. If your icon set name follows the `*icon-theme.json` name scheme, you will get completion support and hovers in VS Code.
+
+### Icon Set File
+
+The icon set file is a JSON file consisting of file icon associations and icon definitions.
+
+An icon association maps a file type ('file', 'folder', 'json-file'...) to an icon definition. Icon definitions define where the icon is located: That can be an image file or also glyph in a font.
+
+### Icon definitions
+
+The `iconDefinitions` section contains all definitions. Each definition has an id, which will be used to reference the definition. A definition can be referenced also by more than one file association.
+
+```json
+{
+  "iconDefinitions": {
+    "_folder_dark": {
+      "iconPath": "./images/Folder_16x_inverse.svg"
+    }
+  }
+}
+```
+
+This icon definition above contains a definition with the identifier `_folder_dark`.
+
+The following properties are supported:
+
+- `iconPath`: When using a svg/png: the path to the image.
+- `fontCharacter`: When using a glyph font: The character in the font to use.
+- `fontColor`: When using a glyph font: The color to use for the glyph.
+- `fontSize`: When using a font: The font size. By default, the size specified in the font specification is used. Should be a relative size (e.g. 150%) to the parent font size.
+- `fontId`: When using a font: The id of the font. If not specified, the first font specified in font specification section will be picked.
+
+### File association
+
+Icons can be associated to folders, folder names, files, file extensions, file names and [language ids](/api/references/contribution-points#contributes.languages).
+
+Additionally each of these associations can be refined for 'light' and 'highContrast' color themes.
+
+Each file association points to an icon definition.
+
+```json
+{
+  "file": "_file_dark",
+  "folder": "_folder_dark",
+  "folderExpanded": "_folder_open_dark",
+  "folderNames": {
+    ".vscode": "_vscode_folder"
+  },
+  "fileExtensions": {
+    "ini": "_ini_file"
+  },
+  "fileNames": {
+    "win.ini": "_win_ini_file"
+  },
+  "languageIds": {
+    "ini": "_ini_file"
+  },
+  "light": {
+    "folderExpanded": "_folder_open_light",
+    "folder": "_folder_light",
+    "file": "_file_light",
+    "fileExtensions": {
+      "ini": "_ini_file_light"
+    }
+  },
+  "highContrast": {}
+}
+```
+
+- `file` is the default file icon, shown for all files that don't match any extension, filename or language id. Currently all properties defined by the definition of the file icon will be inherited (only relevant for font glyphs, useful for the fontSize).
+- `folder` is the folder icon for collapsed folders, and if `folderExpanded` is not set, also for expanded folders. Icons for specific folder names can be associated using the `folderNames` property.
+  The folder icon is optional. If not set, no icon will be shown for folder.
+- `folderExpanded` is the folder icon for expanded folders. The expanded folder icon is optional. If not set, the icon defined for `folder` will be shown.
+- `folderNames` associates folder names to icons. The key of the set is the folder name, not including any path segments. Patterns or wildcards are not supported. Folder name matching is case insensitive.
+- `folderNamesExpanded` associates folder names to icons for expanded folder. The key of the set is the folder name, not including any path segments. Patterns or wildcards are not supported. Folder name matching is case insensitive.
+- `rootFolder` is the folder icon for collapsed workspace root folders , and if `rootFolderExpanded` is not set, also for expanded workspace root folders. If not set, the icon defined for `folder` will be shown for workspace root folders.
+- `rootFolderExpanded` is the folder icon for expanded workspace root folders. If not set, the icon defined for `rootFolder` will be shown for exanded workspace root folders.
+- `languageIds` associates languages to icons. The key in the set is the language id as defined in the [language contribution point](/api/references/contribution-points#contributes.languages). The language of a file is evaluated based on the file extensions and file names as defined in the language contribution. Note that the 'first line match' of the language contribution is not considered.
+- `fileExtensions` associates file extensions to icons. The key in the set is the file extension name. The extension name is a file name segment after a dot (not including the dot). File names with multiple dots such as `lib.d.ts` can match multiple extensions; 'd.ts' and 'ts'. Extensions are compared case insensitive.
+- `fileNames` associates file names to icons. The key in the set is the full file name, not including any path segments. Patterns or wildcards are not supported. File name matching is case insensitive. A 'fileName' match is the strongest match, and the icon associated to the file name will be preferred over an icon of a matching fileExtension and also of a matching language Id.
+
+A file extension match is preferred over a language match, but is weaker than a file name match.
+
+The `light` and the `highContrast` section have the same file association properties as just listed. They allow to override icons for the corresponding themes.
+
+### Font definitions
+
+The `fonts` section lets you declare any number of glyph fonts that you want to use.
+You can later reference these fonts in the icon definitions. The font declared first will be used as the default if an icon definition does not specify a font id.
+
+Copy the font file into your extension and set the path accordingly.
+It is recommended to use [WOFF](https://developer.mozilla.org/docs/Web/Guide/WOFF) fonts.
+
+- Set 'woff' as the format.
+- the weight property values are defined [here](https://developer.mozilla.org/docs/Web/CSS/font-weight#Values).
+- the style property values are defined [here](https://developer.mozilla.org/docs/Web/CSS/@font-face/font-style#Values).
+- the size should be relative to the font size where the icon is used. Therefore, always use percentage.
+
+```json
+{
+  "fonts": [
+    {
+      "id": "turtles-font",
+      "src": [
+        {
+          "path": "./turtles.woff",
+          "format": "woff"
+        }
+      ],
+      "weight": "normal",
+      "style": "normal",
+      "size": "150%"
+    }
+  ],
+  "iconDefinitions": {
+    "_file": {
+      "fontCharacter": "\\E002",
+      "fontColor": "#5f8b3b",
+      "fontId": "turtles-font"
+    }
+  }
+}
+```
+
+### Folder icons in File Icon Themes
+
+File Icon themes can instruct the File Explorer not to show the default folder icon (the rotating triangles or "twisties") when the folder icons are good enough to indicate the expansion state of a folder. This mode is enabled by setting `"hidesExplorerArrows":true` in the File Icon theme definition file.