You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for your interest in helping develop this extension. If you're new to developing VSCode extensions, then you may want to try and follow the quickstart below. If something doesn't work, feel free to open an issue or submit a PR fixing this documentation!
3
+
Thank you for your interest in helping develop this extension. To get up and running, follow the guide below. If something doesn't work, feel free to open an issue or submit a PR fixing this documentation!
4
4
5
5
## Quickstart
6
6
@@ -13,29 +13,33 @@ Thank you for your interest in helping develop this extension. If you're new to
13
13
1. You can manually test your changes by navigating to "Run and Debug" -> "Run Extension" -> green arrow. This opens a sandboxed version of vscode with your updated extension.
14
14
1. You should add unit tests for your functionality as well. These go under `src/test/suite`, or in `src/lib.rs` if you are modifying the rust code. *Your PR will likely not be merged without unit tests.*
15
15
16
-
# Release check list
16
+
# Maintaining this extension
17
+
18
+
The following items are relevant if you are actively maintaining this extension. I wrote this documentation for myself, since I have to do these maintenance actions approximately once a year at this point.
19
+
20
+
## Release check list
17
21
18
22
You will need [`vsce`](https://github.com/Microsoft/vscode-vsce) installed.
19
23
20
-
If it has expired, get a new token. Follow the instructions [here](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token).
24
+
If needed, get a new access token. Follow the instructions [here](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token).
21
25
22
26
1. The [CHANGELOG](./CHANGELOG.md) has been updated.
23
-
1.`git checkout master`
27
+
1.`git checkout main`
24
28
1.`git pull`
25
29
1. Smoke test (run extension through debugger, open `smoke_test.py`, press `enter` after each line and make sure it looks good).
26
-
1. CI has passed on the master branch.
27
-
1.`vsce publish {patch,minor,major}`
30
+
1. CI has passed on the main branch.
31
+
1.`vsce publish {patch,minor,major}` and optionally use the `--pre-release` argumentvs
28
32
1.`vsce package`
29
33
1.`git push; git push --tags`
30
34
1. On GitHub, draft a release using the existing tag that was created by the `publish` command.
31
35
* If you are not told that the tag already exists, then you have a typo, or you missed a step.
32
36
1. Attach the `.vsix` artifact created by the `package` command to the draft release.
33
37
1. Publish the release.
34
38
35
-
# Getting CI to work
39
+
##Getting CI to work
36
40
37
-
...
41
+
Follow the instructions [here](https://code.visualstudio.com/api/working-with-extensions/continuous-integration#github-actions).
Copy file name to clipboardExpand all lines: README.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,8 @@ Correct Python indentation in Visual Studio Code. See the extension on the [VSCo
6
6
7
7
Theme shown is _Community Theme Palenight_ from [_Community Material Theme_](https://marketplace.visualstudio.com/items?itemName=Equinusocio.vsc-community-material-theme) v1.4.4.
[](https://marketplace.visualstudio.com/items?itemName=KevinRose.vsc-python-indent)
11
-
[](https://marketplace.visualstudio.com/items?itemName=KevinRose.vsc-python-indent)
0 commit comments