|
|
|
|
@@ -70,7 +70,7 @@ The tabs in this article allow you to switch between information for each of the
|
|
|
|
|
|
|
|
|
|
## Working in a codespace in a JetBrains IDE
|
|
|
|
|
|
|
|
|
|
To use {% data variables.product.prodname_github_codespaces %} with a JetBrains IDE you must have already installed JetBrains Gateway. For information about installing JetBrains Gateway, see [the jetbrains.com website](https://www.jetbrains.com/remote-development/gateway/).
|
|
|
|
|
To use {% data variables.product.prodname_github_codespaces %} with a JetBrains IDE you must have already installed JetBrains Gateway. For information about installing JetBrains Gateway, see [the JetBrains website](https://www.jetbrains.com/remote-development/gateway/).
|
|
|
|
|
|
|
|
|
|
You can work in a codespace using your choice of JetBrains IDE. After creating a codespace, you can use the JetBrains Gateway application to open the codespace in your preferred IDE.
|
|
|
|
|
|
|
|
|
|
@@ -78,16 +78,20 @@ You can edit code, debug, and use Git commands while developing in a codespace w
|
|
|
|
|
|
|
|
|
|
### IntelliJ IDEA user interface
|
|
|
|
|
|
|
|
|
|
Within the {% data variables.product.prodname_github_codespaces %} documentation we use IntelliJ IDEA as a representative JetBrains IDE.
|
|
|
|
|
Within the {% data variables.product.prodname_github_codespaces %} documentation we use IntelliJ IDEA as a representative JetBrains IDE. Different JetBrains IDEs may have different layouts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. **Navigation bar** - This displays the path to the currently selected file or directory. Use the buttons to the right of the navigation bar to perform various actions, including building, running, or debugging the project, or running Git commands to commit and push your changes.
|
|
|
|
|
2. **Project tool window** - This shows you the structure of your project and allows you to open files in the editor.
|
|
|
|
|
3. **{% data variables.product.prodname_github_codespaces %} tool window** - This is displayed by clicking the {% data variables.product.prodname_github_codespaces %} plugin in the bar to the left of the tool window. It displays information about your codespace, including its display name and machine type.
|
|
|
|
|
3. **{% data variables.product.prodname_github_codespaces %} tool window** - This is displayed by clicking the {% data variables.product.prodname_github_codespaces %} plugin in the bar to the left of the tool window. It displays information about your codespace, including its display name and machine type. The buttons at the top of this tool window allow you to:
|
|
|
|
|
* Stop the codespace and disconnect
|
|
|
|
|
* Display the "Your codespaces" web page
|
|
|
|
|
* View the codespace creation logs
|
|
|
|
|
* Rebuild the dev container
|
|
|
|
|
4. **Editor** - This is where you edit your files. You can right-click the tab for a file to access options such as moving the tab to a new window.
|
|
|
|
|
5. **Terminal** - This is displayed by clicking **Terminal** in the tool window bar at the bottom of the main window (just above the status bar). The integrated terminal allows you to perform command-line tasks without having to switch to a dedicated terminal application.
|
|
|
|
|
6. **Status bar** - Position the mouse pointer over the icon at the left of the status bar to see a list of tools. Click the icon to hide or show the tool window bars. The right side of the status bar shows information about the project, including the current Git branch.
|
|
|
|
|
6. **Status bar** - Hover over the icon at the left of the status bar to see a list of tools. Click the icon to hide or show the tool window bars. The right side of the status bar shows information about the project, including the current Git branch.
|
|
|
|
|
|
|
|
|
|
For more information about the IntelliJ IDEA user interface, see the [JetBrains documentation for IntelliJ IDEA](https://www.jetbrains.com/help/idea/guided-tour-around-the-user-interface.html).
|
|
|
|
|
|
|
|
|
|
@@ -103,7 +107,7 @@ You can use a [dotfiles](https://dotfiles.github.io/tutorials/) repository to pe
|
|
|
|
|
|
|
|
|
|
Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit your changes. Committing changes to your repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, to modify the configuration of codespaces created for a repository, will be available to everybody who uses the repository.
|
|
|
|
|
|
|
|
|
|
For information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
|
|
|
|
|
For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
|
|
|
|
|
|
|
|
|
|
## Further reading
|
|
|
|
|
|
|
|
|
|
|
hubwriter