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 #35002

Open
1 task done
nguyenalex836 opened this issue Oct 18, 2024 · 2 comments · May be fixed by #35081
Labels
Codespaces Content relating to GitHub Codespaces content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers

Comments

@nguyenalex836
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/codespaces/developing-in-a-codespace/using-github-codespaces-in-your-jetbrains-ide#the-jetbrains-remote-development-connection-process

This issue is intended for newcomers to the OS Docs repo! 💛

If you are veteran of the OS Docs repo and are looking for issues to work on, take a look at our help wanted section

What part(s) of the article would you like to see updated?

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.

Update this unordered list to an ordered list

Additional information

No response

@nguyenalex836 nguyenalex836 added good first issue Good for newcomers content This issue or pull request belongs to the Docs Content team Codespaces Content relating to GitHub Codespaces labels Oct 18, 2024
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 18, 2024
@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team label Oct 18, 2024
@JP-sDEV
Copy link

JP-sDEV commented Oct 18, 2024

Hi could I attempt to fix this issue?

@nguyenalex836
Copy link
Contributor Author

Hi could I attempt to fix this issue?

@JP-sDEV Of course! 💛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Codespaces Content relating to GitHub Codespaces content This issue or pull request belongs to the Docs Content team good first issue Good for newcomers
Projects
None yet
2 participants