Skip to content

Commit

Permalink
[clangd] Add brief instructions on how to make a release for vscode-c…
Browse files Browse the repository at this point in the history
…langd extension.

Reviewers: sammccall

Subscribers: klimek, ilya-biryukov, jkorous-apple, ioeric, cfe-commits

Differential Revision: https://reviews.llvm.org/D43455

llvm-svn: 325499
  • Loading branch information
hokein committed Feb 19, 2018
1 parent 3289ab2 commit 359406f
Showing 1 changed file with 25 additions and 0 deletions.
25 changes: 25 additions & 0 deletions clang-tools-extra/clangd/clients/clangd-vscode/README.md
Expand Up @@ -49,3 +49,28 @@ point to the binary.
$ code .
# When VS Code starts, press <F5>.
```

## Publish to VS Code Marketplace

New changes to `clangd-vscode` are not released until a new version is published
to the marketplace.

### Requirements

* Make sure install the `vsce` command (`npm install -g vsce`)
* `llvm-vs-code-extensions` account
* Bump the version in `package.json`, and commit the change to upstream

The extension is published under `llvm-vs-code-extensions` account, which is
currently maintained by clangd developers. If you want to make a new release,
please contact cfe-dev@lists.llvm.org.

### Steps

```bash
$ cd /path/to/clang-tools-extra/clangd/clients/clangd-vscode/
# For the first time, you need to login in the account. vsce will ask you for
the account password, and remember it for future commands.
$ vsce login llvm-vs-code-extensions
$ vsce publish
```

0 comments on commit 359406f

Please sign in to comment.