From 5d5605cf7d55c89f3cdf7ce6d68a73a2d68f4f61 Mon Sep 17 00:00:00 2001 From: Rachael Sewell Date: Mon, 25 Sep 2023 11:31:32 -0700 Subject: [PATCH] fix incorrect code languages --- .../supplemental-arguments-and-settings.md | 4 ++-- ...epository-management-policies-in-your-enterprise.md | 2 +- .../using-ssh-over-the-https-port.md | 2 +- .../using-source-control-in-your-codespace.md | 4 ++-- ...eshooting-gpg-verification-for-github-codespaces.md | 10 +++++----- .../quickstart-for-tasklists.md | 2 +- .../creating-a-github-pages-site-with-jekyll.md | 2 +- data/reusables/gpg/configure-gpg-signing.md | 2 +- data/reusables/gpg/set-auto-sign.md | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-) diff --git a/content/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings.md b/content/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings.md index 46c713430d..7f51bae83f 100644 --- a/content/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings.md +++ b/content/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings.md @@ -51,7 +51,7 @@ A credentials file must be a YAML file containing a list of server and access to For example: -```yml +```yaml - url: https://github.com access_token: ghp_mygeneraltoken - url: https://github.com/specific_org/ @@ -69,7 +69,7 @@ For the above credentials file, {% data variables.product.prodname_actions_impor For example: -```yml +```yaml - url: https://gitlab.com access_token: super_secret_token provider: gitlab diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md index c056176d11..546908dd0f 100644 --- a/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md +++ b/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md @@ -297,7 +297,7 @@ The unauthenticated git protocol on port 9418 is no longer supported. If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. Run the following commands after your upgrade: -```ShellSession +```shell sudo ghe-config app.gitauth.git-protocol true sudo ghe-config-apply ``` diff --git a/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 315baf7ec7..b51b51175c 100644 --- a/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -66,7 +66,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %} The first time you interact with {% data variables.product.prodname_dotcom %} after switching to port 443, you may get a warning message that the host wasn't found in `known_hosts`, or that it was found by another name. -```ShellSession +```shell > The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established. > ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU. > This host key is known by the following other names/addresses: diff --git a/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index dbf3c270bb..fefb9efdf3 100644 --- a/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -74,13 +74,13 @@ When {% data variables.product.prodname_github_codespaces %} creates a fork, or By default, source control commands that you access from your editor's user interface, such as the **Sync Changes** button in {% data variables.product.prodname_vscode_shortname %}, target your fork. If you're working from the command line, you can use `origin` to refer to your fork and `upstream` to refer to the upstream repository. For example, you can fetch changes from the upstream repository to ensure your codespace is up to date with the latest changes to the project. -```Shell +```shell git fetch upstream ``` When you have made some changes, you can push them to a feature branch of your fork. -```Shell +```shell git push origin my-feature-branch ``` diff --git a/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md b/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md index 162fae3e18..af81e4d479 100644 --- a/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md +++ b/content/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces.md @@ -30,7 +30,7 @@ If you have disabled GPG verification, and are working in an existing codespace, To keep making regular, unsigned commits in your codespace, reset `commit.gpgsign` to the default value of `false` by entering the following command in the terminal. -```Shell copy +```shell copy git config --unset commit.gpgsign ``` @@ -54,7 +54,7 @@ To sign your commits with GPG, {% data variables.product.prodname_github_codespa To check that these values are set correctly in a codespace, you can use the `git config --list --show-origin` command. Because {% data variables.product.prodname_github_codespaces %} sets this configuration at the system level, the required configuration settings should come from `/usr/local/etc/gitconfig`. -```Shell +```shell $ git config --list --show-origin file:/usr/local/etc/gitconfig credential.helper=/.codespaces/bin/gitcredential_github.sh file:/usr/local/etc/gitconfig user.name=Mona Lisa @@ -82,7 +82,7 @@ For example, if the global `.gitconfig` file on your local machine contains a `g 1. On your local machine, open a terminal. 1. To remove the conflicting value from `~/.gitconfig` (Mac/Linux) or `C:\Users\YOUR-USER\.gitconfig` (Windows), use the `git config --global --unset` command. - ```Shell + ```shell git config --global --unset gpg.program ``` @@ -91,13 +91,13 @@ For example, if the global `.gitconfig` file on your local machine contains a `g For example, you can use the `--system` flag to set the configuration in the system-level file at `PATH/etc/gitconfig`, where `PATH` is the directory in which Git is installed on your system. - ```Shell + ```shell git config --system gpg.program gpg2 ``` Alternatively, if your dotfiles repository contains an installation script in a recognized file such as `install.sh`, you can use the `$CODESPACES` environment variable to add conditional logic, such as only setting `gpg.program` when you are not in a codespace. In the following example, `-z "$CODESPACES"` returns `true` if you are not in a codespace. -```Shell copy +```shell copy if [ -z "$CODESPACES" ]; then git config --global gpg.program gpg2 fi diff --git a/content/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists.md b/content/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists.md index 9c588e0ab8..a46387dbe5 100644 --- a/content/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists.md +++ b/content/issues/managing-your-tasks-with-tasklists/quickstart-for-tasklists.md @@ -100,7 +100,7 @@ You can create multiple tasklists in a single issue. Each tasklist has its own t 1. In the menu, click **Edit**. 1. In the issue description, below your first tasklist, add the Markdown below: - ````markdown{:copy} + ````markdown copy ```[tasklist] ### Tasks - [ ] Draft task diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index 09e25df6a8..f4512db255 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -105,7 +105,7 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages % 1. From the command line, run `bundle install`. 1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory. For more information, see "[AUTOTITLE](/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository)." - ```yml + ```yaml domain: my-site.github.io # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com url: https://my-site.github.io # the base hostname and protocol for your site, e.g. http://example.com baseurl: /REPOSITORY-NAME/ # place folder name if the site is served in a subfolder diff --git a/data/reusables/gpg/configure-gpg-signing.md b/data/reusables/gpg/configure-gpg-signing.md index 08d11bd3c2..5c627330c5 100644 --- a/data/reusables/gpg/configure-gpg-signing.md +++ b/data/reusables/gpg/configure-gpg-signing.md @@ -1,5 +1,5 @@ 1. If you have previously configured Git to use a different key format when signing with `--gpg-sign`, unset this configuration so the default format of `openpgp` will be used. - ```Shell + ```shell git config --global --unset gpg.format ``` diff --git a/data/reusables/gpg/set-auto-sign.md b/data/reusables/gpg/set-auto-sign.md index d9bd30a14d..04385ba485 100644 --- a/data/reusables/gpg/set-auto-sign.md +++ b/data/reusables/gpg/set-auto-sign.md @@ -1,6 +1,6 @@ 1. Optionally, to configure Git to sign all commits by default, enter the following command: - ```Shell + ```shell git config --global commit.gpgsign true ```