Go to file
2016-02-26 10:19:23 +01:00
.vscode Add "launch"-type config to launch.json 2016-02-18 22:54:45 -08:00
build use same cli script in Windows 2016-02-25 17:35:33 +01:00
extensions add reload javascript project command 2016-02-25 15:05:14 +01:00
resources use same cli script in Windows 2016-02-25 17:35:33 +01:00
scripts Merge pull request #3103 from jamesqo/patch-1 2016-02-18 17:12:46 +01:00
src indentation: store indentation in history only if editor configuration changed by user 2016-02-26 10:00:17 +01:00
test more reliable tests in ci 2016-02-09 11:17:15 +01:00
.editorconfig Fixed comments 2015-11-28 13:23:56 +07:00
.gitignore build deb in .build/linux 2016-02-12 11:07:18 +01:00
.travis.yml use latest node in travis 2016-02-19 10:27:09 +01:00
appveyor.yml move back to ATOM_SHELL_INTERNAL_RUN_AS_NODE 2016-02-15 11:07:22 +01:00
CONTRIBUTING.md Update CONTRIBUTING.md 2015-12-10 15:40:00 +01:00
gulpfile.js Fix remaining 'super' must be called before accessing 'this' errors 2016-02-23 14:19:14 +01:00
LICENSE.txt Hello Code 2015-11-13 14:39:38 +01:00
npm-shrinkwrap.json add "bindings" and "nan" into our shrinkwrap file for "weak" module 2016-02-08 17:18:32 +01:00
OSSREADME.json remove csharp/omnisharp dependencies from top level ossreadme 2016-02-26 10:19:23 +01:00
package.json remove plugin host sourcemap 2016-02-19 15:10:46 +01:00
product.json win32ShortcutName -> applicationName 2016-02-12 15:48:47 +01:00
README.md Added feedback information 2016-02-08 17:36:44 -08:00
ThirdPartyNotices.txt update ThirdPartyNotices.txt 2016-02-23 17:02:46 +01:00
tslint.json Port noUnexternalizedStringsRule to TS 1.8.0. Add support to detect duplicate keys with different messages 2016-02-18 09:12:42 +01:00

Visual Studio Code - Open Source

Build Status Build status

VS Code is a new type of tool that combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. Code provides comprehensive editing and debugging support, an extensibility model, and lightweight integration with existing tools.

vscodereadme

The vscode repository is where we do development and there are many ways you can participate in the project, for example:

Contributing

If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute, which covers the following:

Feedback

Many of the core components and extensions to Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter

For a complete list, please see the Related Projects page on our wiki.

License

MIT