Skip to content

Commit e9a7ba3

Browse files
committed
docs: add details to updating vscode section
1 parent caee285 commit e9a7ba3

File tree

1 file changed

+14
-10
lines changed

1 file changed

+14
-10
lines changed

doc/CONTRIBUTING.md

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,15 @@
22
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
33
# Contributing
44

5-
- [Pull Requests](#pull-requests)
6-
- [Requirements](#requirements)
7-
- [Development Workflow](#development-workflow)
8-
- [Updating VS Code](#updating-vs-code)
9-
- [Build](#build)
10-
- [Structure](#structure)
11-
- [Modifications to VS Code](#modifications-to-vs-code)
12-
- [Currently Known Issues](#currently-known-issues)
5+
- [Contributing](#contributing)
6+
- [Pull Requests](#pull-requests)
7+
- [Requirements](#requirements)
8+
- [Development Workflow](#development-workflow)
9+
- [Updating VS Code](#updating-vs-code)
10+
- [Build](#build)
11+
- [Structure](#structure)
12+
- [Modifications to VS Code](#modifications-to-vs-code)
13+
- [Currently Known Issues](#currently-known-issues)
1314

1415
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
1516

@@ -58,10 +59,13 @@ To develop inside an isolated Docker container:
5859

5960
### Updating VS Code
6061

61-
If you need to update VS Code, you can update the subtree with one line. Here's an example using the version 1.52.1
62+
If you need to update VS Code, you can update the subtree with one line. Here's an example using the version 1.52:
6263

6364
```shell
64-
git subtree pull --prefix lib/vscode vscode release/1.52 --squash --message "Update VS Code to 1.52.1"
65+
# Add vscode as a new remote if you haven't already and fetch
66+
git remote add -f vscode https://github.com/microsoft/vscode.git
67+
68+
git subtree pull --prefix lib/vscode vscode release/1.52 --squash --message "Update VS Code to 1.52"
6569
```
6670

6771
## Build

0 commit comments

Comments
 (0)