Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
79 changes: 0 additions & 79 deletions .github/workflows/update.yaml

This file was deleted.

8 changes: 8 additions & 0 deletions docs/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -257,6 +257,14 @@ Most of the meaty parts are in the Code portion of the codebase under
Our modifications to Code can be found in the [patches](../patches) directory.
We pull in Code as a submodule pointing to an upstream release branch.

This fork does not bump that submodule itself. Code updates arrive by merging
[coder/code-server](https://github.com/coder/code-server), whose scheduled job
does the bump and refreshes the patch stack against the new release; taking
them from there means we review one upstream merge instead of owning the
rebase. `ci/build/update-vscode.sh` is still here for the manual case: run it
with no `VERSION` to re-refresh the patches and regenerate the webview CSP
hashes when a merge leaves them conflicting.

In v1 of code-server, we had Code as a submodule and used a single massive patch
that split the codebase into a front-end and a server. The front-end consisted
of the UI code, while the server ran the extensions and exposed an API to the
Expand Down
Loading