Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to ordered list in using-github-codespaces-in-your-jetbrains-ide#the-jetbrains-remote-development-connection-process #35081

Merged
merged 5 commits into from
Nov 1, 2024
Merged
Changes from 4 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
Original file line number Diff line number Diff line change
Expand Up @@ -32,13 +32,12 @@
### The JetBrains remote development connection process

The basic process behind using a codespace in your JetBrains IDE is as follows.

* In the JetBrains Gateway application you select one of your active or stopped codespaces.
* You then choose which JetBrains IDE you want to use.
* The selected JetBrains IDE is then downloaded to the remote virtual machine that hosts your codespace and source code.
* The JetBrains thin client application is then downloaded to your local machine and started.
* The client application connects to the full backend IDE.
* You can work on your code in the client application in just the same way you would in a local environment.
1. In the JetBrains Gateway application you select one of your active or stopped codespaces.
2. You then choose which JetBrains IDE you want to use.

Check failure on line 36 in content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md

View workflow job for this annotation

GitHub Actions / lint-content

Ordered list item prefix

Expected: 1; Actual: 2; Style: 1/1/1.
3. The selected JetBrains IDE is then downloaded to the remote virtual machine that hosts your codespace and source code.

Check failure on line 37 in content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md

View workflow job for this annotation

GitHub Actions / lint-content

Ordered list item prefix

Expected: 1; Actual: 3; Style: 1/1/1.
4. The JetBrains thin client application is then downloaded to your local machine and started.

Check failure on line 38 in content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md

View workflow job for this annotation

GitHub Actions / lint-content

Ordered list item prefix

Expected: 1; Actual: 4; Style: 1/1/1.
5. The client application connects to the full backend IDE.

Check failure on line 39 in content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md

View workflow job for this annotation

GitHub Actions / lint-content

Ordered list item prefix

Expected: 1; Actual: 5; Style: 1/1/1.
6. You can work on your code in the client application in just the same way you would in a local environment.

Check failure on line 40 in content/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide.md

View workflow job for this annotation

GitHub Actions / lint-content

Ordered list item prefix

Expected: 1; Actual: 6; Style: 1/1/1.

## Prerequisites

Expand Down
Loading