- 07 5月, 2020 3 次提交
-
-
由 Anmol Sethi 提交于
Add npm package and document/cleanup CI and build process
-
由 Anmol Sethi 提交于
-
由 Anmol Sethi 提交于
Closes many issues that I'll prune after adding more docs for users.
-
- 06 5月, 2020 3 次提交
- 05 5月, 2020 2 次提交
-
-
由 Anmol Sethi 提交于
Unset $PASSWORD after grabbing it
-
由 Anmol Sethi 提交于
Closes #1583
-
- 02 5月, 2020 2 次提交
-
-
由 Asher 提交于
Fixes #1549.
-
由 Anmol Sethi 提交于
fix macOS spelling
-
- 01 5月, 2020 1 次提交
-
-
由 saxc 提交于
-
- 30 4月, 2020 5 次提交
-
-
由 Asher 提交于
-
由 Asher 提交于
Remove transformer file
-
由 Asher 提交于
Things got really out of whack when trying to update dependencies earlier.
-
由 Asher 提交于
Also remove some unused imports that were causing build errors (they were left over from the fix that allowed installing any extension kind).
-
由 Asher 提交于
-
- 29 4月, 2020 12 次提交
-
-
由 Asher 提交于
This enables vscode-icons among others.
-
由 Asher 提交于
- Fix priority to match the commented behavior. - Ignore bogus LOG_LEVEL values.
-
由 Asher 提交于
I managed to lose this deletion in a merge.
-
由 Anmol Sethi 提交于
-
由 Anmol Sethi 提交于
-
由 Anmol Sethi 提交于
Deprecate --host and --port in favour of --bind-addr
-
由 Anmol Sethi 提交于
Add basic rate limiting to login endpoint
-
由 Anmol Sethi 提交于
Closes #1320
-
由 Anmol Sethi 提交于
-
由 Anmol Sethi 提交于
-
由 Anmol Sethi 提交于
Remove SSH server
-
由 Anmol Sethi 提交于
-
- 28 4月, 2020 1 次提交
-
-
由 Asher 提交于
Pass the user data dir to the browser environment service then derive all the paths we can based off that path like the global storage path which the vim extension uses to store history (otherwise it gets stored in the working directory from when code-server was spawned). Arguably the better solution is to use the userdata scheme but that won't work because the vim extension ignores the VS Code API. Fixes #1551.
-
- 27 4月, 2020 1 次提交
-
-
由 Anmol Sethi 提交于
Closes #1502
-
- 23 4月, 2020 2 次提交
-
-
由 Anmol Sethi 提交于
Fix code-server.sh script on macOS
-
由 Anmol Sethi 提交于
-
- 22 4月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 21 4月, 2020 2 次提交
- 18 4月, 2020 1 次提交
-
-
由 Asher 提交于
See #1532 for more context. - Errored JSON requests will get back the error in JSON instead of using the status text. This seems better to me because it seems more correct to utilize the response body over hijacking the status text. The caller is expecting JSON anyway. Worst of all I never actually set the status text like I thought I did so it wasn't working to begin with. - Allow the update error to propagate for JSON update requests. It was caught to show the error inline instead of an error page when using the update page but for JSON requests it meant there was no error and no error code so it looked like it succeeded. - Make errors for failed requests to GitHub less incomprehensible. Previously they would just be the code which is no context at all.
-
- 17 4月, 2020 2 次提交
-
-
由 Anmol Sethi 提交于
Closes #1425
-
由 Asher 提交于
Fixes #1535.
-
- 15 4月, 2020 1 次提交
-
-
由 Charles Moog 提交于
-
- 14 4月, 2020 1 次提交
-
-
由 Asher 提交于
Fixes #1507.
-