5839299a49
* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * Update script to skip checked in list of files to reset for broken translations * Temporarily enable all langauges to check CI status * Need better performance for more languages * Revert "Update script to skip checked in list of files to reset for broken translations" This reverts commit f88f01a0f790fcd9fba5fc79937edd923263b6c5. * Revert changes used to test CI passes when all languages are enabled Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
69 lines
3.9 KiB
Markdown
69 lines
3.9 KiB
Markdown
---
|
|
title: Using the Visual Studio Code Command Palette in Codespaces
|
|
intro: 'You can use the Command Palette feature of {% data variables.product.prodname_vscode %} to access many commands in Codespaces.'
|
|
versions:
|
|
fpt: '*'
|
|
ghec: '*'
|
|
type: reference
|
|
topics:
|
|
- Codespaces
|
|
- Visual Studio Code
|
|
product: '{% data reusables.gated-features.codespaces %}'
|
|
shortTitle: VS Code Command Palette
|
|
allowTitleToDifferFromFilename: true
|
|
redirect_from:
|
|
- /codespaces/codespaces-reference/using-the-command-palette-in-codespaces
|
|
---
|
|
|
|
## About the {% data variables.product.prodname_vscode %} Command Palette
|
|
|
|
The Command Palette is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in Codespaces. The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information on using the {% data variables.product.prodname_vscode_command_palette %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the Visual Studio Code documentation.
|
|
|
|
## Accessing the {% data variables.product.prodname_vscode_command_palette %}
|
|
|
|
You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways.
|
|
|
|
- `Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows).
|
|
|
|
Note that this command is a reserved keyboard shortcut in Firefox.
|
|
- `F1`
|
|
- From the Application Menu, click **View > Command Palette…**.
|
|
|
|
|
|
|
|
## Commands for {% data variables.product.prodname_github_codespaces %}
|
|
|
|
To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "Codespaces".
|
|
|
|
|
|
|
|
### Suspending or stopping a codespace
|
|
|
|
If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes.
|
|
|
|
To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**.
|
|
|
|
|
|
|
|
### Adding a dev container from a template
|
|
|
|
To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
|
|
|
|
|
|
|
|
### Rebuilding a codespace
|
|
|
|
If you add a dev container or edit any of the configuration files (`devcontainer.json` and `Dockerfile`), you'll have to rebuild your codespace for it to apply your changes.
|
|
|
|
To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
|
|
|
|
|
|
|
|
### Codespaces logs
|
|
|
|
You can use the {% data variables.product.prodname_vscode_command_palette %} to access the codespace creation logs, or you can use it export all logs.
|
|
|
|
To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to Codespaces or select **Codespaces: View Creation Logs** to view logs related to the setup.
|
|
|
|
|