diff --git a/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-registry.md b/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-registry.md index 15faf6b1d9..cf24fdfe36 100644 --- a/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-registry.md +++ b/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-registry.md @@ -71,7 +71,7 @@ If you are setting the secrets at the user or organization level, make sure to a For a private image registry in Azure, you could create the following secrets: -``` +```shell ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io ACR_CONTAINER_REGISTRY_USER = acr-user-here ACR_CONTAINER_REGISTRY_PASSWORD = @@ -87,7 +87,7 @@ Once you've added the secrets, you may need to stop and then start the codespace To access AWS Elastic Container Registry (ECR), you can provide an AWS access key ID and secret key, and {% data variables.product.prodname_dotcom %} can retrieve an access token for you and log in on your behalf. -``` +```shell *_CONTAINER_REGISTRY_SERVER = *_CONTAINER_REGISTRY_USER = *_CONTAINER_REGISTRY_PASSWORD = @@ -95,9 +95,9 @@ To access AWS Elastic Container Registry (ECR), you can provide an AWS access k You must also ensure you have the appropriate AWS IAM permissions to perform the credential swap (e.g. `sts:GetServiceBearerToken`) as well as the ECR read operation (either `AmazonEC2ContainerRegistryFullAccess` or `ReadOnlyAccess`). -Alternatively, if you don't want GitHub to perform the credential swap on your behalf, you can provide an authorization token fetched via AWS's APIs or CLI. +Alternatively, if you don't want {% data variables.product.prodname_dotcom %} to perform the credential swap on your behalf, you can provide an authorization token fetched via AWS's APIs or CLI. -``` +```shell *_CONTAINER_REGISTRY_SERVER = *_CONTAINER_REGISTRY_USER = AWS *_CONTAINER_REGISTRY_PASSWORD = diff --git a/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md index 07a190ca46..322ec4fbc7 100644 --- a/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md +++ b/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md @@ -63,13 +63,13 @@ You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variable 1. To view your list of codespaces, in a terminal, enter the following command. - ``` + ```shell gh codespace list ``` 1. Optionally, to find the current machine type for a codespace, enter the following command. - ``` + ```shell gh api /user/codespaces/CODESPACE-NAME ``` @@ -80,14 +80,14 @@ You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variable Details for the current machine are listed under the `machine` field. 1. To find the available machine types for a codespace, enter the following command. - ``` + ```shell gh api /user/codespaces/CODESPACE-NAME/machines ``` Replace `CODESPACE-NAME` with the permanent name of the codespace, for example `octocat-literate-space-parakeet-mld5`. 1. To change the machine type for a codespace, enter the following command. - ``` + ```shell gh codespace edit --machine MACHINE-TYPE-NAME ``` diff --git a/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 9c02b8fb46..80746ffaa2 100644 --- a/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -107,7 +107,7 @@ By default you are prompted to confirm deletion of any codespaces that contain u Delete all of the codespaces for the `octo-org/octo-repo` repository that you created more than 7 days ago. -``` +```shell gh codespace delete --repo octo-org/octo-repo --days 7 ``` diff --git a/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index f7a2bcacc1..2be24471fa 100644 --- a/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -146,14 +146,14 @@ Copy the address and paste it somewhere for later use. 1. Start an SSH session for your codespace. - ``` + ```shell gh codespace ssh ``` 1. If you have more than one codespace, select the appropriate codespace from the list that's displayed. 1. Display the `GITHUB_TOKEN`. - ``` + ```shell echo $GITHUB_TOKEN ``` @@ -169,7 +169,7 @@ Copy the address and paste it somewhere for later use. 1. Exit the SSH session. - ``` + ```shell exit ``` diff --git a/content/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files.md b/content/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files.md index e719765d32..8ed65f7949 100644 --- a/content/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files.md +++ b/content/codespaces/developing-in-codespaces/persisting-environment-variables-and-temporary-files.md @@ -36,7 +36,7 @@ There are three ways that you can set persistent custom environment variables fo Edit the `devcontainer.json` configuration file for the repository, and use the `remoteEnv` property to set the environment variable value: -``` +```json { "remoteEnv": { "VARNAME": "value" diff --git a/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md b/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md index cd6cffae17..899a8e867c 100644 --- a/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md +++ b/content/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository.md @@ -20,7 +20,7 @@ If you're trying to push to or pull from the repository from which you created t You may see these errors if you use a dotfiles repository with {% data variables.product.prodname_github_codespaces %}, and you have configured Git to use a protocol other than HTTPS for transferring data to the remote repository. For example, you may have configured Git to use SSH by including lines like the following in a config file in your dotfiles. -``` +```shell [url "git@github.com:"] insteadOf = https://github.com/ ``` diff --git a/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md index 5c903b072b..787b90cc84 100644 --- a/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md +++ b/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md @@ -100,7 +100,7 @@ Some more destructive options: {% data reusables.codespaces.recovery-mode %} -``` +```shell This codespace is currently running in recovery mode due to a container error. ``` diff --git a/content/codespaces/troubleshooting/troubleshooting-included-usage.md b/content/codespaces/troubleshooting/troubleshooting-included-usage.md index 802ddcde92..9c47a8e25c 100644 --- a/content/codespaces/troubleshooting/troubleshooting-included-usage.md +++ b/content/codespaces/troubleshooting/troubleshooting-included-usage.md @@ -71,7 +71,7 @@ devcontainer-info If the dev container for the current codespace was built from the default image, the output of this command will contain the following information. -``` +```shell - Definition ID: universal - Source code repository: https://github.com/devcontainers/images ``` diff --git a/content/copilot/getting-started-with-github-copilot.md b/content/copilot/getting-started-with-github-copilot.md index 6751c6d2af..083f541170 100644 --- a/content/copilot/getting-started-with-github-copilot.md +++ b/content/copilot/getting-started-with-github-copilot.md @@ -424,7 +424,7 @@ If you use Vim/Neovim, you can view and incorporate suggestions from {% data var For guidance on using {% data variables.product.prodname_copilot %} in Vim/Neovim, you can view the plugin documentation. To see the documentation, open Vim/Neovim and run the following command: -``` +```shell :help copilot ``` diff --git a/data/reusables/codespaces/rebuilding-container-procedures.md b/data/reusables/codespaces/rebuilding-container-procedures.md index 47bc6aa4c8..62f5d09912 100644 --- a/data/reusables/codespaces/rebuilding-container-procedures.md +++ b/data/reusables/codespaces/rebuilding-container-procedures.md @@ -12,7 +12,7 @@ If you've changed a dev container configuration outside of {% data variables.pro 1. In a terminal, enter the following command. - ``` + ```shell gh codespace rebuild ``` diff --git a/data/reusables/codespaces/troubleshooting-simple-browser.md b/data/reusables/codespaces/troubleshooting-simple-browser.md index 489349815e..504eb29749 100644 --- a/data/reusables/codespaces/troubleshooting-simple-browser.md +++ b/data/reusables/codespaces/troubleshooting-simple-browser.md @@ -32,7 +32,7 @@ To implement the port configuration specified in `devcontainer.json`, {% data va 1. Verify that the `settings.json` file contains lines like the following. - ``` + ```json "remote.portsAttributes": { "3000": { "label": "Application", diff --git a/data/reusables/codespaces/using-tools-to-access-ports-2.md b/data/reusables/codespaces/using-tools-to-access-ports-2.md index 9e075a8b81..b272fc7351 100644 --- a/data/reusables/codespaces/using-tools-to-access-ports-2.md +++ b/data/reusables/codespaces/using-tools-to-access-ports-2.md @@ -2,7 +2,7 @@ In a terminal on your local computer, enter: -``` +```shell curl ADDRESS -H "X-Github-Token: TOKEN" ``` diff --git a/data/reusables/copilot/config-enable-copilot-in-vimneovim.md b/data/reusables/copilot/config-enable-copilot-in-vimneovim.md index eae2b244a1..d0b2c9d85c 100644 --- a/data/reusables/copilot/config-enable-copilot-in-vimneovim.md +++ b/data/reusables/copilot/config-enable-copilot-in-vimneovim.md @@ -1,11 +1,11 @@ 1. To configure {% data variables.product.prodname_copilot %}, open Vim/Neovim and enter the following command. - ``` + ```shell :Copilot setup ``` 1. Enable {% data variables.product.prodname_copilot %} in your Vim/Neovim configuration, or with the Vim/Neovim command. - ``` + ```shell :Copilot enable ```