Remove unnecessary $ (#38339)

Author: gracepark

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md

@@ -76,7 +76,7 @@ You can use the `git config` command to change the email address you associate w
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. {% data reusables.user-settings.set_your_email_address_in_git %}
    ```shell
-   $ git config --global user.email "YOUR_EMAIL"
+   git config --global user.email "YOUR_EMAIL"
    ```
 3. {% data reusables.user-settings.confirm_git_email_address_correct %}
    ```shell
@@ -95,7 +95,7 @@ You can change the email address associated with commits you make in a single re
 2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
 3. {% data reusables.user-settings.set_your_email_address_in_git %}
    ```shell
-   $ git config user.email "YOUR_EMAIL"
+   git config user.email "YOUR_EMAIL"
    ```
 4. {% data reusables.user-settings.confirm_git_email_address_correct %}
    ```shell

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md

@@ -39,5 +39,5 @@ If you've been collaborating professionally with another person on repositories
 - Delete local copies of your forks that may exist on your computer:
 
 ```shell
-$ rm -rf WORK_DIRECTORY
+rm -rf WORK_DIRECTORY
 ```

content/actions/creating-actions/creating-a-docker-container-action.md

@@ -134,7 +134,7 @@ Next, the script gets the current time and sets it as an output variable that ac
 1. Optionally, to check the permission mode of the file in the git index, run the following command.
 
    ```shell copy
-   $ git ls-files --stage entrypoint.sh
+   git ls-files --stage entrypoint.sh
    ```
 
    An output like `100755 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0       entrypoint.sh` means the file has the executable permission. In this example, `755` denotes the executable permission.

content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md

@@ -75,13 +75,13 @@ This procedure demonstrates how to create the service account for your GKE integ
 1. Create a new service account:
    {% raw %}
    ```
-   $ gcloud iam service-accounts create $SA_NAME
+   gcloud iam service-accounts create $SA_NAME
    ```
   {% endraw %}
 1. Retrieve the email address of the service account you just created:
    {% raw %}
    ```
-   $ gcloud iam service-accounts list
+   gcloud iam service-accounts list
    ```
   {% endraw %}
 1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
@@ -101,13 +101,13 @@ This procedure demonstrates how to create the service account for your GKE integ
 1. Download the JSON keyfile for the service account:
    {% raw %}
    ```
-   $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
+   gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
    ```
    {% endraw %}
 1. Store the service account key as a secret named `GKE_SA_KEY`:
    {% raw %}
    ```
-   $ export GKE_SA_KEY=$(cat key.json | base64)
+   export GKE_SA_KEY=$(cat key.json | base64)
    ```
    {% endraw %}
    For more information about how to store a secret, see "[AUTOTITLE](/actions/security-guides/encrypted-secrets)."

content/actions/hosting-your-own-runners/managing-self-hosted-runners/monitoring-and-troubleshooting-self-hosted-runners.md

@@ -129,7 +129,7 @@ actions.runner.octo-org-octo-repo.hostname.service loaded active running GitHub
 You can use `journalctl` to monitor the real-time activity of the self-hosted runner:
 
 ```shell
-$ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f
+sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f
 ```
 
 In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status:

content/actions/migrating-to-github-actions/automated-migrations/automating-migration-with-github-actions-importer.md

@@ -54,15 +54,15 @@ You can use {% data variables.product.prodname_actions_importer %} to migrate fr
 To ensure you're running the latest version of {% data variables.product.prodname_actions_importer %}, you should regularly run the `update` command:
 
 ```bash
-$ gh actions-importer update
+gh actions-importer update
 ```
 
 ### Authenticating at the command line
 
 You must configure credentials that allow {% data variables.product.prodname_actions_importer %} to communicate with {% data variables.product.prodname_dotcom %} and your current CI server. You can configure these credentials using environment variables or a `.env.local` file. The environment variables can be configured in an interactive prompt, by running the following command:
 
 ```bash
-$ gh actions-importer configure
+gh actions-importer configure
 ```
 
 ## Using the {% data variables.product.prodname_actions_importer %} CLI

content/actions/security-guides/encrypted-secrets.md

@@ -393,7 +393,7 @@ You can use Base64 encoding to store small binary blobs as secrets. You can then
 1. Use `base64` to encode your file into a Base64 string. For example:
 
    ```
-   $ base64 -i cert.der -o cert.base64
+   base64 -i cert.der -o cert.base64
    ```
 
 1. Create a secret that contains the Base64 string. For example:

content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md

@@ -63,6 +63,6 @@ Your instance validates the hostnames for proxy exclusion using the list of IANA
 1. Enter the following command, replacing COMMA-SEPARATED-TLD-LIST with a comma-separated list of TLDs.
 
    ```shell
-   $ ghe-config noproxy.exception-tld-list "COMMA-SEPARATED-TLD-LIST"
+   ghe-config noproxy.exception-tld-list "COMMA-SEPARATED-TLD-LIST"
    ```
 {% data reusables.enterprise.apply-configuration %}

content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md

@@ -68,11 +68,11 @@ We do not recommend customizing UFW as it can complicate some troubleshooting is
 1. Configure a custom firewall rule.
 2. Check the status of each new rule with the `status numbered` command.
    ```shell
-   $ sudo ufw status numbered
+   sudo ufw status numbered
    ```
 3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file.
    ```shell
-   $ sudo cp -r /etc/ufw ~/ufw.backup
+   sudo cp -r /etc/ufw ~/ufw.backup
    ```
 
 After you upgrade {% data variables.location.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules.
@@ -90,11 +90,11 @@ If something goes wrong after you change the firewall rules, you can reset the r
 {% data reusables.enterprise_installation.ssh-into-instance %}
 2. To restore the previous backup rules, copy them back to the firewall with the `cp` command.
    ```shell
-   $ sudo cp -f ~/ufw.backup/*rules /etc/ufw
+   sudo cp -f ~/ufw.backup/*rules /etc/ufw
    ```
 3. Restart the firewall with the `systemctl` command.
    ```shell
-   $ sudo systemctl restart ufw
+   sudo systemctl restart ufw
    ```
 4. Confirm that the rules are back to their defaults with the `ufw status` command.
    ```shell

content/admin/configuration/configuring-your-enterprise/command-line-utilities.md

@@ -117,7 +117,7 @@ $ ghe-config -l
 Allows you to find the universally unique identifier (UUID) of your node in `cluster.conf`.
 
 ```shell
-  $ ghe-config HOSTNAME.uuid
+  ghe-config HOSTNAME.uuid
 ```
 
 Allows you to exempt a list of users from REST API rate limits. A hard limit of 120,000 requests will still apply to these users. Usernames you provide for this command are case-sensitive. For more information, see "[AUTOTITLE](/rest/overview/resources-in-the-rest-api#rate-limiting)."
@@ -278,7 +278,7 @@ ghe-org-admin-promote -a
 Use this command to immediately unlock the {% data variables.enterprise.management_console %} after {% ifversion enterprise-authentication-rate-limits %}an account lockout. To configure authentication policies for {% data variables.location.product_location %}, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-authentication-policy-rate-limits)".{% else %}10 failed login attempts in the span of 10 minutes.{% endif %}
 
 ```shell
-$ ghe-reactivate-admin-login
+ghe-reactivate-admin-login
 ```
 
 ### ghe-saml-mapping-csv
@@ -410,7 +410,7 @@ This utility allows you to configure the primary network interface.
 To enter visual mode, which will guide you through configuration of network settings:
 
 ```shell
-$ ghe-setup-network -v
+ghe-setup-network -v
 ```
 
 Use the -h flag for additional options.
@@ -420,7 +420,7 @@ Use the -h flag for additional options.
 This utility checks the existing SSH host keys against the list of known leaked SSH host keys.
 
 ```shell
-$ ghe-ssh-check-host-keys
+ghe-ssh-check-host-keys
 ```
 
 If a leaked host key is found the utility exits with status `1` and a message:
@@ -540,15 +540,15 @@ ghe-ssl-generate-csr
 Some platforms require this script to expand the user volume. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity)".
 
 ```shell
-$ ghe-storage-extend
+ghe-storage-extend
 ```
 
 ### ghe-version
 
 This utility prints the version, platform, and build of {% data variables.location.product_location %}.
 
 ```shell
-$ ghe-version
+ghe-version
 ```
 
 ### ghe-webhook-logs
@@ -583,19 +583,19 @@ This utility allows you to enforce an even distribution of allocations across yo
 To output a list of balanceable jobs and their associated allocation spread:
 
 ```shell
-$ ghe-cluster-balance status
+ghe-cluster-balance status
 ```
 
 To output allocation counts for a given job or comma-delimited list of jobs:
 
 ```shell
-$ ghe-cluster-balance -j JOB
+ghe-cluster-balance -j JOB
 ```
 
 To rebalance problematic allocations for a given job or comma-delimited list of jobs:
 
 ```shell
-$ ghe-cluster-balance rebalance -j JOB
+ghe-cluster-balance rebalance -j JOB
 ```
 
 You can use the following flags with `ghe-cluster-balance rebalance`.
@@ -611,13 +611,13 @@ Flag | Description
 To output completion scripts for the given shell:
 
 ```shell
-$ ghe-cluster-balance completion
+ghe-cluster-balance completion
 ```
 
 To display a short description of the utility and any valid subcommands:
 
 ```shell
-$ ghe-cluster-balance help
+ghe-cluster-balance help
 ```
 
 {% endif %}
@@ -627,7 +627,7 @@ $ ghe-cluster-balance help
 Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
 
 ```shell
-$ ghe-cluster-status
+ghe-cluster-status
 ```
 
 ### ghe-cluster-support-bundle
@@ -640,38 +640,38 @@ By default, the command creates the tarball in _/tmp_, but you can also have it
 
 To create a standard bundle:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
 ```
 
 To create a standard bundle including data from the last 3 hours:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- "ghe-cluster-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}3hours {% elsif ghes < 3.9 %}'3 hours' {% endif %} -o" > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- "ghe-cluster-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}3hours {% elsif ghes < 3.9 %}'3 hours' {% endif %} -o" > support-bundle.tgz
 ```
 
 To create a standard bundle including data from the last 2 days:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- "ghe-cluster-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}2days {% elsif ghes < 3.9 %}'2 days' {% endif %} -o" > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- "ghe-cluster-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}2days {% elsif ghes < 3.9 %}'2 days' {% endif %} -o" > support-bundle.tgz
 ```
 
 To create a standard bundle including data from the last 4 days and 8 hours:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- "ghe-cluster-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}4days8hours {% elsif ghes < 3.9 %}'4 days 8 hours' {% endif %} -o" > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- "ghe-cluster-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}4days8hours {% elsif ghes < 3.9 %}'4 days 8 hours' {% endif %} -o" > support-bundle.tgz
 ```
 
 To create an extended bundle including data from the last 8 days:
 
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
 ```
 
 To send a bundle to {% data variables.contact.github_support %}:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u'
+ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u'
 ```
 
 To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID'
+ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID'
 ```
 
 ### ghe-dpages
@@ -1048,38 +1048,38 @@ By default, the command creates the tarball in _/tmp_, but you can also have it
 
 To create a standard bundle:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz
 ```
 
 To create a standard bundle including data from the last 3 hours:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- "ghe-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}3hours {% elsif ghes < 3.9 %}'3 hours' {% endif %} -o" > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- "ghe-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}3hours {% elsif ghes < 3.9 %}'3 hours' {% endif %} -o" > support-bundle.tgz
 ```
 
 To create a standard bundle including data from the last 2 days:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- "ghe-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}2days {% elsif ghes < 3.9 %}'2 days' {% endif %} -o" > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- "ghe-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}2days {% elsif ghes < 3.9 %}'2 days' {% endif %} -o" > support-bundle.tgz
 ```
 
 To create a standard bundle including data from the last 4 days and 8 hours:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- "ghe-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}4days8hours {% elsif ghes < 3.9 %}'4 days 8 hours' {% endif %} -o" > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- "ghe-support-bundle -p {% ifversion bundle-cli-syntax-no-quotes %}4days8hours {% elsif ghes < 3.9 %}'4 days 8 hours' {% endif %} -o" > support-bundle.tgz
 ```
 
 To create an extended bundle including data from the last 8 days:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz
+ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz
 ```
 
 To send a bundle to {% data variables.contact.github_support %}:
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u'
+ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u'
 ```
 
 To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
 
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID'
+ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID'
 ```
 
 ### ghe-support-upload
@@ -1135,7 +1135,7 @@ A file containing the status of the download is available at _/var/lib/ghe-updat
 To check for the latest {% data variables.product.prodname_enterprise %} release, use the `-i` switch.
 
 ```shell
-$ ssh -p 122 admin@HOSTNAME -- 'ghe-update-check'
+ssh -p 122 admin@HOSTNAME -- 'ghe-update-check'
 ```
 
 ### ghe-upgrade
@@ -1162,7 +1162,7 @@ The `ghe-upgrade-scheduler` utility is best suited for scheduling hotpatch upgra
 
 To schedule a new installation for a package:
 ```shell
-$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME
+ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME
 ```
 
 To show scheduled installations for a package:
@@ -1173,7 +1173,7 @@ $ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME
 
 To remove scheduled installations for a package:
 ```shell
-$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME
+ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME
 ```
 
 ## User management