Skip to content

Commit bd760a6

Browse files
graceparkgracepark
authored
Remove unnecessary $ (#38339)
1 parent a04dc81 commit bd760a6

File tree

125 files changed

+383
-383
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

125 files changed

+383
-383
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ You can use the `git config` command to change the email address you associate w
7676
{% data reusables.command_line.open_the_multi_os_terminal %}
7777
2. {% data reusables.user-settings.set_your_email_address_in_git %}
7878
```shell
79-
$ git config --global user.email "YOUR_EMAIL"
79+
git config --global user.email "YOUR_EMAIL"
8080
```
8181
3. {% data reusables.user-settings.confirm_git_email_address_correct %}
8282
```shell
@@ -95,7 +95,7 @@ You can change the email address associated with commits you make in a single re
9595
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.
9696
3. {% data reusables.user-settings.set_your_email_address_in_git %}
9797
```shell
98-
$ git config user.email "YOUR_EMAIL"
98+
git config user.email "YOUR_EMAIL"
9999
```
100100
4. {% data reusables.user-settings.confirm_git_email_address_correct %}
101101
```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‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,5 +39,5 @@ If you've been collaborating professionally with another person on repositories
3939
- Delete local copies of your forks that may exist on your computer:
4040

4141
```shell
42-
$ rm -rf WORK_DIRECTORY
42+
rm -rf WORK_DIRECTORY
4343
```

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Next, the script gets the current time and sets it as an output variable that ac
134134
1. Optionally, to check the permission mode of the file in the git index, run the following command.
135135

136136
```shell copy
137-
$ git ls-files --stage entrypoint.sh
137+
git ls-files --stage entrypoint.sh
138138
```
139139

140140
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‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -75,13 +75,13 @@ This procedure demonstrates how to create the service account for your GKE integ
7575
1. Create a new service account:
7676
{% raw %}
7777
```
78-
$ gcloud iam service-accounts create $SA_NAME
78+
gcloud iam service-accounts create $SA_NAME
7979
```
8080
{% endraw %}
8181
1. Retrieve the email address of the service account you just created:
8282
{% raw %}
8383
```
84-
$ gcloud iam service-accounts list
84+
gcloud iam service-accounts list
8585
```
8686
{% endraw %}
8787
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
101101
1. Download the JSON keyfile for the service account:
102102
{% raw %}
103103
```
104-
$ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
104+
gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
105105
```
106106
{% endraw %}
107107
1. Store the service account key as a secret named `GKE_SA_KEY`:
108108
{% raw %}
109109
```
110-
$ export GKE_SA_KEY=$(cat key.json | base64)
110+
export GKE_SA_KEY=$(cat key.json | base64)
111111
```
112112
{% endraw %}
113113
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‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ actions.runner.octo-org-octo-repo.hostname.service loaded active running GitHub
129129
You can use `journalctl` to monitor the real-time activity of the self-hosted runner:
130130

131131
```shell
132-
$ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f
132+
sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f
133133
```
134134

135135
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‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -54,15 +54,15 @@ You can use {% data variables.product.prodname_actions_importer %} to migrate fr
5454
To ensure you're running the latest version of {% data variables.product.prodname_actions_importer %}, you should regularly run the `update` command:
5555

5656
```bash
57-
$ gh actions-importer update
57+
gh actions-importer update
5858
```
5959

6060
### Authenticating at the command line
6161

6262
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:
6363

6464
```bash
65-
$ gh actions-importer configure
65+
gh actions-importer configure
6666
```
6767

6868
## Using the {% data variables.product.prodname_actions_importer %} CLI

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -393,7 +393,7 @@ You can use Base64 encoding to store small binary blobs as secrets. You can then
393393
1. Use `base64` to encode your file into a Base64 string. For example:
394394
395395
```
396-
$ base64 -i cert.der -o cert.base64
396+
base64 -i cert.der -o cert.base64
397397
```
398398
399399
1. Create a secret that contains the Base64 string. For example:

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,6 @@ Your instance validates the hostnames for proxy exclusion using the list of IANA
6363
1. Enter the following command, replacing COMMA-SEPARATED-TLD-LIST with a comma-separated list of TLDs.
6464

6565
```shell
66-
$ ghe-config noproxy.exception-tld-list "COMMA-SEPARATED-TLD-LIST"
66+
ghe-config noproxy.exception-tld-list "COMMA-SEPARATED-TLD-LIST"
6767
```
6868
{% data reusables.enterprise.apply-configuration %}

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -68,11 +68,11 @@ We do not recommend customizing UFW as it can complicate some troubleshooting is
6868
1. Configure a custom firewall rule.
6969
2. Check the status of each new rule with the `status numbered` command.
7070
```shell
71-
$ sudo ufw status numbered
71+
sudo ufw status numbered
7272
```
7373
3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file.
7474
```shell
75-
$ sudo cp -r /etc/ufw ~/ufw.backup
75+
sudo cp -r /etc/ufw ~/ufw.backup
7676
```
7777

7878
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
9090
{% data reusables.enterprise_installation.ssh-into-instance %}
9191
2. To restore the previous backup rules, copy them back to the firewall with the `cp` command.
9292
```shell
93-
$ sudo cp -f ~/ufw.backup/*rules /etc/ufw
93+
sudo cp -f ~/ufw.backup/*rules /etc/ufw
9494
```
9595
3. Restart the firewall with the `systemctl` command.
9696
```shell
97-
$ sudo systemctl restart ufw
97+
sudo systemctl restart ufw
9898
```
9999
4. Confirm that the rules are back to their defaults with the `ufw status` command.
100100
```shell

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

Lines changed: 29 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ $ ghe-config -l
117117
Allows you to find the universally unique identifier (UUID) of your node in `cluster.conf`.
118118

119119
```shell
120-
$ ghe-config HOSTNAME.uuid
120+
ghe-config HOSTNAME.uuid
121121
```
122122

123123
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
278278
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 %}
279279

280280
```shell
281-
$ ghe-reactivate-admin-login
281+
ghe-reactivate-admin-login
282282
```
283283

284284
### ghe-saml-mapping-csv
@@ -410,7 +410,7 @@ This utility allows you to configure the primary network interface.
410410
To enter visual mode, which will guide you through configuration of network settings:
411411

412412
```shell
413-
$ ghe-setup-network -v
413+
ghe-setup-network -v
414414
```
415415

416416
Use the -h flag for additional options.
@@ -420,7 +420,7 @@ Use the -h flag for additional options.
420420
This utility checks the existing SSH host keys against the list of known leaked SSH host keys.
421421

422422
```shell
423-
$ ghe-ssh-check-host-keys
423+
ghe-ssh-check-host-keys
424424
```
425425

426426
If a leaked host key is found the utility exits with status `1` and a message:
@@ -540,15 +540,15 @@ ghe-ssl-generate-csr
540540
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)".
541541

542542
```shell
543-
$ ghe-storage-extend
543+
ghe-storage-extend
544544
```
545545

546546
### ghe-version
547547

548548
This utility prints the version, platform, and build of {% data variables.location.product_location %}.
549549

550550
```shell
551-
$ ghe-version
551+
ghe-version
552552
```
553553

554554
### ghe-webhook-logs
@@ -583,19 +583,19 @@ This utility allows you to enforce an even distribution of allocations across yo
583583
To output a list of balanceable jobs and their associated allocation spread:
584584

585585
```shell
586-
$ ghe-cluster-balance status
586+
ghe-cluster-balance status
587587
```
588588

589589
To output allocation counts for a given job or comma-delimited list of jobs:
590590

591591
```shell
592-
$ ghe-cluster-balance -j JOB
592+
ghe-cluster-balance -j JOB
593593
```
594594

595595
To rebalance problematic allocations for a given job or comma-delimited list of jobs:
596596

597597
```shell
598-
$ ghe-cluster-balance rebalance -j JOB
598+
ghe-cluster-balance rebalance -j JOB
599599
```
600600

601601
You can use the following flags with `ghe-cluster-balance rebalance`.
@@ -611,13 +611,13 @@ Flag | Description
611611
To output completion scripts for the given shell:
612612

613613
```shell
614-
$ ghe-cluster-balance completion
614+
ghe-cluster-balance completion
615615
```
616616

617617
To display a short description of the utility and any valid subcommands:
618618

619619
```shell
620-
$ ghe-cluster-balance help
620+
ghe-cluster-balance help
621621
```
622622

623623
{% endif %}
@@ -627,7 +627,7 @@ $ ghe-cluster-balance help
627627
Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
628628

629629
```shell
630-
$ ghe-cluster-status
630+
ghe-cluster-status
631631
```
632632

633633
### ghe-cluster-support-bundle
@@ -640,38 +640,38 @@ By default, the command creates the tarball in _/tmp_, but you can also have it
640640

641641
To create a standard bundle:
642642
```shell
643-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
643+
ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
644644
```
645645

646646
To create a standard bundle including data from the last 3 hours:
647647
```shell
648-
$ 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
648+
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
649649
```
650650

651651
To create a standard bundle including data from the last 2 days:
652652
```shell
653-
$ 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
653+
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
654654
```
655655

656656
To create a standard bundle including data from the last 4 days and 8 hours:
657657
```shell
658-
$ 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
658+
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
659659
```
660660

661661
To create an extended bundle including data from the last 8 days:
662662

663663
```shell
664-
$ ssh -p 122 admin@HOSTNAME -- ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
664+
ssh -p 122 admin@HOSTNAME -- ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
665665
```
666666
667667
To send a bundle to {% data variables.contact.github_support %}:
668668
```shell
669-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u'
669+
ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u'
670670
```
671671
672672
To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
673673
```shell
674-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID'
674+
ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID'
675675
```
676676
677677
### ghe-dpages
@@ -1048,38 +1048,38 @@ By default, the command creates the tarball in _/tmp_, but you can also have it
10481048
10491049
To create a standard bundle:
10501050
```shell
1051-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz
1051+
ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz
10521052
```
10531053
10541054
To create a standard bundle including data from the last 3 hours:
10551055
```shell
1056-
$ 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
1056+
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
10571057
```
10581058
10591059
To create a standard bundle including data from the last 2 days:
10601060
```shell
1061-
$ 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
1061+
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
10621062
```
10631063
10641064
To create a standard bundle including data from the last 4 days and 8 hours:
10651065
```shell
1066-
$ 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
1066+
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
10671067
```
10681068
10691069
To create an extended bundle including data from the last 8 days:
10701070
```shell
1071-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz
1071+
ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz
10721072
```
10731073
10741074
To send a bundle to {% data variables.contact.github_support %}:
10751075
```shell
1076-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u'
1076+
ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u'
10771077
```
10781078
10791079
To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
10801080
10811081
```shell
1082-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID'
1082+
ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID'
10831083
```
10841084
10851085
### ghe-support-upload
@@ -1135,7 +1135,7 @@ A file containing the status of the download is available at _/var/lib/ghe-updat
11351135
To check for the latest {% data variables.product.prodname_enterprise %} release, use the `-i` switch.
11361136
11371137
```shell
1138-
$ ssh -p 122 admin@HOSTNAME -- 'ghe-update-check'
1138+
ssh -p 122 admin@HOSTNAME -- 'ghe-update-check'
11391139
```
11401140
11411141
### ghe-upgrade
@@ -1162,7 +1162,7 @@ The `ghe-upgrade-scheduler` utility is best suited for scheduling hotpatch upgra
11621162
11631163
To schedule a new installation for a package:
11641164
```shell
1165-
$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME
1165+
ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME
11661166
```
11671167
11681168
To show scheduled installations for a package:
@@ -1173,7 +1173,7 @@ $ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME
11731173
11741174
To remove scheduled installations for a package:
11751175
```shell
1176-
$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME
1176+
ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME
11771177
```
11781178
11791179
## User management

0 commit comments

Comments
 (0)