(empty token)
+info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - USERNAME (empty token)
```
This error means that {% data variables.product.prodname_desktop %} is unable to find the access token that it created in the system keychain.
diff --git a/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md b/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
index c0f1fec257..b0f93f2234 100644
--- a/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
+++ b/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
@@ -16,13 +16,13 @@ versions:
3. {% data reusables.desktop.launch-desktop-from-command-line %}
```shell
- $ github /path/to/repo
+ $ github /path/to/repo
```
You can also change to your repository path and then type `github .` to open that repository.
```shell
- $ cd /path/to/repo
+ $ cd /path/to/repo
[repo]$ github .
```
@@ -34,13 +34,13 @@ versions:
2. {% data reusables.desktop.launch-desktop-from-command-line %}
```shell
- C:\Users\octocat> github path\to\repo
+ C:\Users\octocat> github path\to\repo
```
You can also change to your repository path and then type `github .` to open that repository.
```shell
- C:\Users\octocat> cd repo\myrepo
+ C:\Users\octocat> cd repo\myrepo
C:\Users\octocat\repo\myrepo> github .
```
diff --git a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
index e25b98006d..a8274a92fa 100644
--- a/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
+++ b/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
@@ -48,7 +48,7 @@ To verify a private key:
2. Generate the fingerprint of your private key (PEM) locally by using the following command:
```shell
- $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl sha256 -binary | openssl base64
+ $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl sha256 -binary | openssl base64
```
3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
diff --git a/content/developers/overview/using-ssh-agent-forwarding.md b/content/developers/overview/using-ssh-agent-forwarding.md
index cb7a2ce912..a0f3e4dfa2 100644
--- a/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/content/developers/overview/using-ssh-agent-forwarding.md
@@ -32,7 +32,7 @@ You can test that your local key works by entering `ssh -T git@{% ifversion ghes
```shell
$ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
# Attempt to SSH in to github
-> Hi username! You've successfully authenticated, but GitHub does not provide
+> Hi USERNAME! You've successfully authenticated, but GitHub does not provide
> shell access.
```
@@ -68,7 +68,7 @@ If the variable is not set, it means that agent forwarding is not working:
```shell
$ echo "$SSH_AUTH_SOCK"
# Print out the SSH_AUTH_SOCK variable
-> [No output]
+> [No output]
$ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
# Try to SSH to github
> Permission denied (publickey).
@@ -84,7 +84,7 @@ SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the `.git/confi
```shell
[remote "origin"]
- url = git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}:yourAccount/yourProject.git
+ url = git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}:YOUR_ACCOUNT/YOUR_PROJECT.git
fetch = +refs/heads/*:refs/remotes/origin/*
```
@@ -97,10 +97,10 @@ Before you can make your keys work through agent forwarding, they must work loca
Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal:
```shell
-$ ssh -v example.com
+$ ssh -v "example.com"
# Connect to example.com with verbose debug output
> OpenSSH_8.1p1, LibreSSL 2.7.3
-> debug1: Reading configuration data /Users/you/.ssh/config
+> debug1: Reading configuration data /Users/YOU/.ssh/config
> debug1: Applying options for example.com
> debug1: Reading configuration data /etc/ssh_config
> debug1: Applying options for *
@@ -147,7 +147,7 @@ ssh-add -L
If the command says that no identity is available, you'll need to add your key:
```shell
-$ ssh-add yourkey
+$ ssh-add YOUR-KEY
```
{% tip %}
@@ -155,7 +155,7 @@ $ ssh-add yourkey
On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command:
```shell
-$ ssh-add -K yourkey
+$ ssh-add -K YOUR-KEY
```
{% endtip %}
diff --git a/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
index 4bfb12f6f5..d4828309cd 100644
--- a/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
+++ b/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
@@ -30,7 +30,7 @@ To set your token on GitHub:
Next, set up an environment variable on your server that stores this token. Typically, this is as simple as running:
```shell
-$ export SECRET_TOKEN=your_token
+$ export SECRET_TOKEN=YOUR-TOKEN
```
**Never** hardcode the token into your app!
diff --git a/content/get-started/getting-started-with-git/about-remote-repositories.md b/content/get-started/getting-started-with-git/about-remote-repositories.md
index 612bb78690..3eb395163b 100644
--- a/content/get-started/getting-started-with-git/about-remote-repositories.md
+++ b/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -34,7 +34,7 @@ You can use the `git remote add` command to match a remote URL with a name.
For example, you'd type the following in the command line:
```shell
-git remote add origin <REMOTE_URL>
+git remote add origin <REMOTE_URL>
```
This associates the name `origin` with the `REMOTE_URL`.
diff --git a/content/get-started/getting-started-with-git/ignoring-files.md b/content/get-started/getting-started-with-git/ignoring-files.md
index 72d4b8d668..6e098c14d2 100644
--- a/content/get-started/getting-started-with-git/ignoring-files.md
+++ b/content/get-started/getting-started-with-git/ignoring-files.md
@@ -35,7 +35,7 @@ For an example *.gitignore* file, see "[Some common .gitignore configurations](h
If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
```shell
-$ git rm --cached FILENAME
+$ git rm --cached FILENAME
```
## Configuring ignored files for all repositories on your computer
diff --git a/content/get-started/getting-started-with-git/managing-remote-repositories.md b/content/get-started/getting-started-with-git/managing-remote-repositories.md
index 57047746e8..3799d2d88a 100644
--- a/content/get-started/getting-started-with-git/managing-remote-repositories.md
+++ b/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -36,13 +36,13 @@ The `git remote add` command takes two arguments:
For example:
```shell
-$ git remote add origin https://{% data variables.command_line.codeblock %}/user/repo.git
+$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO>.git
# Set a new remote
$ git remote -v
# Verify new remote
-> origin https://{% data variables.command_line.codeblock %}/user/repo.git (fetch)
-> origin https://{% data variables.command_line.codeblock %}/user/repo.git (push)
+> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (fetch)
+> origin https://{% data variables.command_line.codeblock %}/USER/REPO.git (push)
```
For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
@@ -77,11 +77,11 @@ The `git remote set-url` command takes two arguments:
* A new URL for the remote. For example:
* If you're updating to use HTTPS, your URL might look like:
```shell
-https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git
+https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git
```
* If you're updating to use SSH, your URL might look like:
```shell
-git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
+git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
```
### Switching remote URLs from SSH to HTTPS
@@ -91,19 +91,19 @@ git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY
3. List your existing remotes in order to get the name of the remote you want to change.
```shell
$ git remote -v
- > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch)
- > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push)
+ > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch)
+ > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push)
```
4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
```shell
- $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
+ $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
```
5. Verify that the remote URL has changed.
```shell
$ git remote -v
# Verify new remote URL
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push)
```
The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user-settings.password-authentication-deprecation %}
@@ -117,19 +117,19 @@ You can [use a credential helper](/github/getting-started-with-github/caching-yo
3. List your existing remotes in order to get the name of the remote you want to change.
```shell
$ git remote -v
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push)
```
4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
```shell
- $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
+ $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
```
5. Verify that the remote URL has changed.
```shell
$ git remote -v
# Verify new remote URL
- > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch)
- > origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push)
+ > origin git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (fetch)
+ > origin git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (push)
```
### Troubleshooting: No such remote '[name]'
@@ -158,16 +158,16 @@ These examples assume you're [cloning using HTTPS](/github/getting-started-with-
```shell
$ git remote -v
# View existing remotes
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
$ git remote rename origin destination
# Change remote name from 'origin' to 'destination'
$ git remote -v
# Verify remote's new name
-> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
-> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> destination https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
```
### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]'
@@ -179,8 +179,8 @@ You can check which remotes currently exist with the `git remote -v` command:
```shell
$ git remote -v
# View existing remotes
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
```
### Troubleshooting: Remote [new name] already exists
@@ -203,22 +203,22 @@ These examples assume you're [cloning using HTTPS](/github/getting-started-with-
```shell
$ git remote -v
# View current remotes
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
-> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch)
-> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push)
+> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch)
+> destination https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push)
$ git remote rm destination
# Remove remote
$ git remote -v
# Verify it's gone
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
-> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch)
+> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push)
```
{% warning %}
-**Note**: `git remote rm` does not delete the remote repository from the server. It simply
+**Note**: `git remote rm` does not delete the remote repository from the server. It simply
removes the remote and its references from your local repository.
{% endwarning %}
diff --git a/content/get-started/getting-started-with-git/setting-your-username-in-git.md b/content/get-started/getting-started-with-git/setting-your-username-in-git.md
index 76e3656c32..d4c7186cad 100644
--- a/content/get-started/getting-started-with-git/setting-your-username-in-git.md
+++ b/content/get-started/getting-started-with-git/setting-your-username-in-git.md
@@ -24,7 +24,7 @@ Changing the name associated with your Git commits using `git config` will only
2. {% data reusables.user-settings.set_your_git_username %}
```shell
- $ git config --global user.name "Mona Lisa"
+ $ git config --global user.name "Mona Lisa"
```
3. {% data reusables.user-settings.confirm_git_username_correct %}
@@ -41,7 +41,7 @@ Changing the name associated with your Git commits using `git config` will only
3. {% data reusables.user-settings.set_your_git_username %}
```shell
- $ git config user.name "Mona Lisa"
+ $ git config user.name "Mona Lisa"
```
3. {% data reusables.user-settings.confirm_git_username_correct %}
diff --git a/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
index e206e73052..38ccb5ee1c 100644
--- a/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
+++ b/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
@@ -40,7 +40,7 @@ Through the command line, you can use the credential helper directly to erase th
$ git credential-osxkeychain erase
host={% data variables.command_line.codeblock %}
protocol=https
-> [Press Return]
+> [Press Return]
```
If it's successful, nothing will print out. To test that it works, try and clone a private repository from {% data variables.product.product_location %}. If you are prompted for a password, the keychain entry was deleted.
diff --git a/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md b/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
index eb649b3f6c..2e04cd85a8 100644
--- a/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
+++ b/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
@@ -86,7 +86,7 @@ If you have existing source code or repositories stored locally on your computer
8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
```shell
- $ git remote add origin <REMOTE_URL>
+ $ git remote add origin <REMOTE_URL>
# Sets the new remote
$ git remote -v
# Verifies the new remote URL
@@ -132,7 +132,7 @@ If you have existing source code or repositories stored locally on your computer
8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
```shell
- $ git remote add origin <REMOTE_URL>
+ $ git remote add origin <REMOTE_URL>
# Sets the new remote
$ git remote -v
# Verifies the new remote URL
@@ -178,7 +178,7 @@ If you have existing source code or repositories stored locally on your computer
8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
```shell
- $ git remote add origin <REMOTE_URL>
+ $ git remote add origin <REMOTE_URL>
# Sets the new remote
$ git remote -v
# Verifies the new remote URL
diff --git a/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
index 1ded6370dc..15aceafdb9 100644
--- a/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
+++ b/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
@@ -31,17 +31,17 @@ For purposes of demonstration, we'll use:
1. [Create a new repository on {% data variables.product.product_name %}](/articles/creating-a-new-repository). You'll import your external Git repository to this new repository.
2. On the command line, make a "bare" clone of the repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data.
```shell
- $ git clone --bare https://external-host.com/extuser/repo.git
+ $ git clone --bare https://external-host.com/EXTUSER/REPO.git
# Makes a bare clone of the external repository in a local directory
```
3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
```shell
- $ cd repo.git
- $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/repo.git
+ $ cd REPO.git
+ $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/REPO.git
# Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}
```
4. Remove the temporary local repository.
```shell
$ cd ..
- $ rm -rf repo.git
+ $ rm -rf REPO.git
```
diff --git a/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md b/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md
index 2192e4a51b..de2b2a2489 100644
--- a/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md
+++ b/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md
@@ -26,9 +26,9 @@ Subversion checkouts are different: they mix the repository data in the working
3. Make an empty checkout of the repository:
```shell
- $ svn co --depth empty https://github.com/user/repo
+ $ svn co --depth empty https://github.com/USER/REPO
> Checked out revision 1.
- $ cd repo
+ $ cd REPO
```
4. Get the `trunk` branch. The Subversion bridge maps trunk to the Git HEAD branch.
@@ -74,7 +74,7 @@ You can also confirm the new branch via the command line:
```shell
$ git fetch
-> From https://github.com/user/repo/
+> From https://github.com/USER/REPO/
> * [new branch] more_awesome -> origin/more_awesome
```
@@ -107,13 +107,13 @@ $ svn commit -m 'Test coverage for problems'
To switch between branches, you'll probably want to start with a checkout of `trunk`:
```shell
-$ svn co --depth empty https://github.com/user/repo/trunk
+$ svn co --depth empty https://github.com/USER/REPO/trunk
```
Then, you can switch to another branch:
```shell
-$ svn switch https://github.com/user/repo/branches/more_awesome
+$ svn switch https://github.com/USER/REPO/branches/more_awesome
```
## Finding the Git commit SHA for a Subversion commit
@@ -123,7 +123,7 @@ GitHub's Subversion server exposes the Git commit sha for each Subversion commit
To see the commit SHA, you should ask for the `git-commit` unversioned remote property.
```shell
-$ svn propget git-commit --revprop -r HEAD https://github.com/user/repo
+$ svn propget git-commit --revprop -r HEAD https://github.com/USER/REPO
05fcc584ed53d7b0c92e116cb7e64d198b13c4e3
```
diff --git a/content/get-started/quickstart/contributing-to-projects.md b/content/get-started/quickstart/contributing-to-projects.md
index 3e9ad2b298..70a08fbc3a 100644
--- a/content/get-started/quickstart/contributing-to-projects.md
+++ b/content/get-started/quickstart/contributing-to-projects.md
@@ -58,12 +58,12 @@ You can clone your fork with the command line, {% data variables.product.prodnam
{% data reusables.command_line.change-current-directory-clone %}
4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+ $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
```
5. Press **Enter**. Your local clone will be created.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+ $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
> Cloning into `Spoon-Knife`...
> remote: Counting objects: 10, done.
> remote: Compressing objects: 100% (8/8), done.
@@ -80,7 +80,7 @@ You can clone your fork with the command line, {% data variables.product.prodnam
To create a clone of your fork, use the `--clone` flag.
```shell
-gh repo fork repository --clone=true
+gh repo fork REPOSITORY --clone=true
```
{% endcli %}
diff --git a/content/get-started/quickstart/fork-a-repo.md b/content/get-started/quickstart/fork-a-repo.md
index 9d3c9526b6..52f7e2ba26 100644
--- a/content/get-started/quickstart/fork-a-repo.md
+++ b/content/get-started/quickstart/fork-a-repo.md
@@ -83,13 +83,13 @@ You might fork a project to propose changes to the upstream, or original, reposi
To create a fork of a repository, use the `gh repo fork` subcommand.
```shell
-gh repo fork repository
+gh repo fork REPOSITORY
```
To create the fork in an organization, use the `--org` flag.
```shell
-gh repo fork repository --org "octo-org"
+gh repo fork REPOSITORY --org "octo-org"
```
{% endcli %}
@@ -109,12 +109,12 @@ Right now, you have a fork of the Spoon-Knife repository, but you do not have th
{% data reusables.command_line.change-current-directory-clone %}
4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+ $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
```
5. Press **Enter**. Your local clone will be created.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+ $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
> Cloning into `Spoon-Knife`...
> remote: Counting objects: 10, done.
> remote: Compressing objects: 100% (8/8), done.
@@ -131,7 +131,7 @@ Right now, you have a fork of the Spoon-Knife repository, but you do not have th
To create a clone of your fork, use the `--clone` flag.
```shell
-gh repo fork repository --clone=true
+gh repo fork REPOSITORY --clone=true
```
{% endcli %}
@@ -163,8 +163,8 @@ When you fork a project in order to propose changes to the original repository,
5. Type `git remote -v` and press **Enter**. You will see the current configured remote repository for your fork.
```shell
$ git remote -v
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
```
6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this:
@@ -175,10 +175,10 @@ When you fork a project in order to propose changes to the original repository,
7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
```shell
$ git remote -v
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
- > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch)
- > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/ YOUR_FORK.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
+ > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (fetch)
+ > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ ORIGINAL_REPOSITORY.git (push)
```
Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
@@ -192,13 +192,13 @@ Now, you can keep your fork synced with the upstream repository with a few Git c
To configure a remote repository for the forked repository, use the `--remote` flag.
```shell
-gh repo fork repository --remote=true
+gh repo fork REPOSITORY --remote=true
```
To specify the remote repository's name, use the `--remote-name` flag.
```shell
-gh repo fork repository --remote-name "main-remote-repo"
+gh repo fork REPOSITORY --remote-name "main-remote-repo"
```
{% endcli %}
diff --git a/content/get-started/using-git/about-git-rebase.md b/content/get-started/using-git/about-git-rebase.md
index 008dcea289..8c091ebe3b 100644
--- a/content/get-started/using-git/about-git-rebase.md
+++ b/content/get-started/using-git/about-git-rebase.md
@@ -31,7 +31,7 @@ Typically, you would use `git rebase` to:
To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
```shell
-$ git rebase --interactive other_branch_name
+$ git rebase --interactive OTHER-BRANCH-NAME
```
## Rebasing commits against a point in time
diff --git a/content/get-started/using-git/about-git-subtree-merges.md b/content/get-started/using-git/about-git-subtree-merges.md
index 3fdd7bdf1d..fc56e8aadb 100644
--- a/content/get-started/using-git/about-git-subtree-merges.md
+++ b/content/get-started/using-git/about-git-subtree-merges.md
@@ -99,7 +99,7 @@ Although we've only added one subproject, any number of subprojects can be incor
When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
```shell
-$ git pull -s subtree remotename branchname
+$ git pull -s subtree REMOTE-NAME BRANCH-NAME
```
For the example above, this would be:
diff --git a/content/get-started/using-git/dealing-with-non-fast-forward-errors.md b/content/get-started/using-git/dealing-with-non-fast-forward-errors.md
index 46e0c1673e..9852f9064a 100644
--- a/content/get-started/using-git/dealing-with-non-fast-forward-errors.md
+++ b/content/get-started/using-git/dealing-with-non-fast-forward-errors.md
@@ -17,7 +17,7 @@ If another person has pushed to the same branch as you, Git won't be able to pus
```shell
$ git push origin main
-> To https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
+> To https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
> ! [rejected] main -> main (non-fast-forward)
> error: failed to push some refs to 'https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git'
> To prevent you from losing history, non-fast-forward updates were rejected
@@ -30,13 +30,13 @@ You can fix this by [fetching and merging](/github/getting-started-with-github/g
```shell
$ git fetch origin
# Fetches updates made to an online repository
-$ git merge origin YOUR_BRANCH_NAME
+$ git merge origin YOUR_BRANCH_NAME
# Merges updates made online with your local work
```
Or, you can simply use `git pull` to perform both commands at once:
```shell
-$ git pull origin YOUR_BRANCH_NAME
+$ git pull origin YOUR_BRANCH_NAME
# Grabs online updates and merges them with your local work
```
diff --git a/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/content/get-started/using-git/getting-changes-from-a-remote-repository.md
index 63fa47a4cd..a37185cd69 100644
--- a/content/get-started/using-git/getting-changes-from-a-remote-repository.md
+++ b/content/get-started/using-git/getting-changes-from-a-remote-repository.md
@@ -23,7 +23,7 @@ These commands are very useful when interacting with [a remote repository](/gith
To grab a complete copy of another user's repository, use `git clone` like this:
```shell
-$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
+$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
# Clones a repository to your computer
```
@@ -49,7 +49,7 @@ Use `git fetch` to retrieve new work done by other people. Fetching from a repos
If you already have a local repository with a remote URL set up for the desired project, you can grab all the new information by using `git fetch *remotename*` in the terminal:
```shell
-$ git fetch remotename
+$ git fetch REMOTE-NAME
# Fetches updates made to a remote repository
```
@@ -62,7 +62,7 @@ Merging combines your local changes with changes made by others.
Typically, you'd merge a remote-tracking branch (i.e., a branch fetched from a remote repository) with your local branch:
```shell
-$ git merge remotename/branchname
+$ git merge REMOTE-NAME/BRANCH-NAME
# Merges updates made online with your local work
```
@@ -71,7 +71,7 @@ $ git merge remotename/branchname
`git pull` is a convenient shortcut for completing both `git fetch` and `git merge `in the same command:
```shell
-$ git pull remotename branchname
+$ git pull REMOTE-NAME BRANCH-NAME
# Grabs online updates and merges them with your local work
```
diff --git a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
index b5c8c33262..fdf805447f 100644
--- a/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
+++ b/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
@@ -23,7 +23,7 @@ The `git push` command takes two arguments:
For example:
```shell
-git push <REMOTENAME> <BRANCHNAME>
+git push REMOTE-NAME BRANCH-NAME
```
As an example, you usually run `git push origin main` to push your local changes
@@ -35,10 +35,10 @@ To rename a branch, you'd use the same `git push` command, but you would add
one more argument: the name of the new branch. For example:
```shell
-git push <REMOTENAME> <LOCALBRANCHNAME>:<REMOTEBRANCHNAME>
+git push REMOTE-NAME LOCAL-BRANCH-NAME:REMOTE-BRANCH-NAME
```
-This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`.
+This pushes the `LOCAL-BRANCH-NAME` to your `REMOTE-NAME`, but it is renamed to `REMOTE-BRANCH-NAME`.
## Dealing with "non-fast-forward" errors
@@ -57,13 +57,13 @@ that have the same names as remote branches.
To push a single tag, you can issue the same command as pushing a branch:
```shell
-git push <REMOTENAME> <TAGNAME>
+git push REMOTE-NAME TAG-NAME
```
To push all your tags, you can type the command:
```shell
-git push <REMOTENAME> --tags
+git push REMOTE-NAME --tags
```
## Deleting a remote branch or tag
@@ -71,12 +71,12 @@ git push <REMOTENAME> --tags
The syntax to delete a branch is a bit arcane at first glance:
```shell
-git push <REMOTENAME> :<BRANCHNAME>
+git push REMOTE-NAME:BRANCH-NAME
```
Note that there is a space before the colon. The command resembles the same steps
you'd take to rename a branch. However, here, you're telling Git to push _nothing_
-into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch
+into `BRANCH-NAME` on `REMOTE-NAME`. Because of this, `git push` deletes the branch
on the remote repository.
## Remotes and forks
@@ -89,7 +89,7 @@ repository, you'd add a new remote URL, typically called `upstream`, to
your local Git clone:
```shell
-git remote add upstream <THEIR_REMOTE_URL>
+git remote add upstream THEIR_REMOTE_URL
```
Now, you can fetch updates and branches from *their* fork:
@@ -101,7 +101,7 @@ git fetch upstream
> remote: Compressing objects: 100% (53/53), done.
> remote: Total 62 (delta 27), reused 44 (delta 9)
> Unpacking objects: 100% (62/62), done.
-> From https://{% data variables.command_line.codeblock %}/octocat/repo
+> From https://{% data variables.command_line.codeblock %}/OCTOCAT/REPO
> * [new branch] main -> upstream/main
```
diff --git a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
index 49eef30c38..53ae26156a 100644
--- a/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
+++ b/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -22,12 +22,12 @@ If you create a new clone of the repository, you won't lose any of your Git hist
4. Clone the repository that contains the subfolder.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME
+ $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME
```
4. Change the current working directory to your cloned repository.
```shell
- $ cd REPOSITORY-NAME
+ $ cd REPOSITORY-NAME
```
5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information:
@@ -47,7 +47,7 @@ If you create a new clone of the repository, you won't lose any of your Git hist
$ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
# Filter the specified branch in your directory and remove empty commits
> Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
- > Ref 'refs/heads/BRANCH-NAME' was rewritten
+ > Ref 'refs/heads/BRANCH-NAME' was rewritten
```
The repository should now only contain the files that were in your subfolder(s).
@@ -67,24 +67,24 @@ If you create a new clone of the repository, you won't lose any of your Git hist
8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
```shell
$ git remote -v
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push)
```
9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
```shell
- git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git
+ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git
```
10. Verify that the remote URL has changed with your new repository name.
```shell
$ git remote -v
# Verify new remote URL
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push)
```
11. Push your changes to the new repository on {% data variables.product.product_name %}.
```shell
- git push -u origin BRANCH-NAME
+ git push -u origin BRANCH-NAME
```
diff --git a/content/github-cli/github-cli/creating-github-cli-extensions.md b/content/github-cli/github-cli/creating-github-cli-extensions.md
index e51a8bd6a9..7c0a984b0e 100644
--- a/content/github-cli/github-cli/creating-github-cli-extensions.md
+++ b/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -35,7 +35,7 @@ You can use the `gh extension create` command to create a project for your exten
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension.
```shell
- gh extension create EXTENSION-NAME
+ gh extension create EXTENSION-NAME
```
1. Follow the printed instructions to finalize and optionally publish your extension.
@@ -47,7 +47,7 @@ You can use the `--precompiled=go` argument to create a Go-based project for you
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=go`.
```shell
- gh extension create --precompiled=go EXTENSION-NAME
+ gh extension create --precompiled=go EXTENSION-NAME
```
1. Follow the printed instructions to finalize and optionally publish your extension.
@@ -59,7 +59,7 @@ You can use the `--precompiled=other` argument to create a project for your non-
1. Set up a new extension by using the `gh extension create` subcommand. Replace `EXTENSION-NAME` with the name of your extension and specify `--precompiled=other`.
```shell
- gh extension create --precompiled=other EXTENSION-NAME
+ gh extension create --precompiled=other EXTENSION-NAME
```
1. Add some initial code for your extension in your compiled language of choice.
@@ -97,7 +97,7 @@ You can use the `--precompiled=other` argument to create a project for your non-
1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
```shell
- gh EXTENSION-NAME
+ gh EXTENSION-NAME
```
1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
@@ -105,7 +105,7 @@ You can use the `--precompiled=other` argument to create a project for your non-
```shell
git init -b main
git add . && git commit -m "initial commit"
- gh repo create gh-EXTENSION-NAME --source=. --public --push
+ gh repo create gh-EXTENSION-NAME --source=. --public --push
```
1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
@@ -217,7 +217,7 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
1. Build your code. For example, with Go, replacing `YOUR-USERNAME` with your GitHub username:
```shell
- go mod init github.com/YOUR-USERNAME/gh-whoami
+ go mod init github.com/YOUR-USERNAME/gh-whoami
go mod tidy
go build
```
@@ -225,7 +225,7 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
1. Verify that your extension works. Replace `EXTENSION-NAME` with the name of your extension. For example, `whoami`.
```shell
- gh EXTENSION-NAME
+ gh EXTENSION-NAME
```
1. From your directory, create a repository to publish your extension. Replace `EXTENSION-NAME` with the name of your extension.
@@ -238,12 +238,12 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
```shell
git init -b main
- echo "gh-EXTENSION-NAME" >> .gitignore
- git add main.go go.* .gitignore && git commit -m'Initial commit'
- gh repo create "gh-EXTENSION-NAME"
+ echo "gh-EXTENSION-NAME" >> .gitignore
+ git add main.go go.* .gitignore && git commit -m 'Initial commit'
+ gh repo create "gh-EXTENSION-NAME"
```
-1. Create a release to share your precompiled extension with others. Compile for each platform you want to support, attaching each binary to a release as an asset. Binary executables attached to releases must follow a naming convention and have a suffix of OS-ARCHITECTURE\[EXTENSION\].
+1. Create a release to share your precompiled extension with others. Compile for each platform you want to support, attaching each binary to a release as an asset. Binary executables attached to releases must follow a naming convention and have a suffix of OS-ARCHITECTURE\[EXTENSION\].
For example, an extension named `whoami` compiled for Windows 64bit would have the name `gh-whoami-windows-amd64.exe` while the same extension compiled for Linux 32bit would have the name `gh-whoami-linux-386`. To see an exhaustive list of OS and architecture combinations recognized by `gh`, see [this source code](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
@@ -258,9 +258,9 @@ For more information, see [`gh help formatting`](https://cli.github.com/manual/g
```shell
git tag v1.0.0
git push origin v1.0.0
- GOOS=windows GOARCH=amd64 go build -o gh-EXTENSION-NAME-windows-amd64.exe
- GOOS=linux GOARCH=amd64 go build -o gh-EXTENSION-NAME-linux-amd64
- GOOS=darwin GOARCH=amd64 go build -o gh-EXTENSION-NAME-darwin-amd64
+ GOOS=windows GOARCH=amd64 go build -o gh-EXTENSION-NAME-windows-amd64.exe
+ GOOS=linux GOARCH=amd64 go build -o gh-EXTENSION-NAME-linux-amd64
+ GOOS=darwin GOARCH=amd64 go build -o gh-EXTENSION-NAME-darwin-amd64
gh release create v1.0.0 ./*amd64*
1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
diff --git a/content/github-cli/github-cli/quickstart.md b/content/github-cli/github-cli/quickstart.md
index 5cc3ec7b96..845ab25fda 100644
--- a/content/github-cli/github-cli/quickstart.md
+++ b/content/github-cli/github-cli/quickstart.md
@@ -30,7 +30,7 @@ shortTitle: Quickstart
To authenticate to {% data variables.product.product_location %}, use the `--hostname` flag.
```shell
- gh auth login --hostname hostname
+ gh auth login --hostname HOSTNAME
```
{% endif %}
diff --git a/content/github-cli/github-cli/using-github-cli-extensions.md b/content/github-cli/github-cli/using-github-cli-extensions.md
index c0f6c663f2..ebf804b607 100644
--- a/content/github-cli/github-cli/using-github-cli-extensions.md
+++ b/content/github-cli/github-cli/using-github-cli-extensions.md
@@ -35,7 +35,7 @@ If the owner and repository are used, `gh` will install the extension using the
To install an extension in development from the current directory, use `.` as the value for the `repo` parameter.
```shell
-gh extension install repo
+gh extension install REPO
```
If you already have an extension by the same name installed, the command will fail. For example, if you have installed `octocat/gh-whoami`, you must uninstall it before installing `hubot/gh-whoami`.
@@ -53,7 +53,7 @@ gh extension list
To update an extension, use the `extensions upgrade` subcommand. Replace the `extension` parameter with the name of the extension.
```shell
-gh extension upgrade extension
+gh extension upgrade EXTENSION
```
To update all installed extensions, use the `--all` flag.
@@ -67,5 +67,5 @@ gh extension upgrade --all
To uninstall an extension, use the `extensions remove` subcommand. Replace the `extension` parameter with the name of the extension.
```shell
-gh extension remove extension
+gh extension remove EXTENSION
```
diff --git a/content/graphql/guides/forming-calls-with-graphql.md b/content/graphql/guides/forming-calls-with-graphql.md
index 5526810b97..e086d40fb2 100644
--- a/content/graphql/guides/forming-calls-with-graphql.md
+++ b/content/graphql/guides/forming-calls-with-graphql.md
@@ -62,7 +62,7 @@ In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In Gr
To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`:
```shell
-curl -H "Authorization: bearer token" -X POST -d " \
+curl -H "Authorization: bearer TOKEN" -X POST -d " \
{ \
\"query\": \"query { viewer { login }}\" \
} \
@@ -90,7 +90,7 @@ GraphQL queries return only the data you specify. To form a query, you must spec
Queries are structured like this:
query {
- JSON objects to return
+ JSON-OBJECT-TO-RETURN
}
For a real-world example, see "[Example query](#example-query)."
@@ -106,8 +106,8 @@ To form a mutation, you must specify three things:
Mutations are structured like this:
mutation {
- mutationName(input: {MutationNameInput!}) {
- MutationNamePayload
+ mutationName(input: {MutationNameInput!}) {
+ MutationNamePayload
}
}
diff --git a/content/graphql/guides/introduction-to-graphql.md b/content/graphql/guides/introduction-to-graphql.md
index 573b706e45..e3da852ff3 100644
--- a/content/graphql/guides/introduction-to-graphql.md
+++ b/content/graphql/guides/introduction-to-graphql.md
@@ -116,7 +116,7 @@ GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This
* You can also run an _introspection query_ of the schema via a `GET` request:
```shell
- $ curl -H "Authorization: bearer token" {% data variables.product.graphql_url_pre %}
+ $ curl -H "Authorization: bearer TOKEN" {% data variables.product.graphql_url_pre %}
```
{% note %}
@@ -130,7 +130,7 @@ GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This
Alternatively, you can pass the `idl` media type to return the results in IDL format, which is a condensed version of the schema:
```shell
- $ curl -H "Authorization: bearer token" -H "Accept: application/vnd.github.v4.idl" \
+ $ curl -H "Authorization: bearer TOKEN" -H "Accept: application/vnd.github.v4.idl" \
{% data variables.product.graphql_url_pre %}
```
diff --git a/content/graphql/guides/using-global-node-ids.md b/content/graphql/guides/using-global-node-ids.md
index 5dadcb4e95..ff9e2ee892 100644
--- a/content/graphql/guides/using-global-node-ids.md
+++ b/content/graphql/guides/using-global-node-ids.md
@@ -35,7 +35,7 @@ Let's walk through an example.
If you [request the authenticated user](/rest/reference/users#get-the-authenticated-user):
```shell
-$ curl -i -u username:token {% data variables.product.api_url_pre %}/user
+$ curl -i -u USERNAME:TOKEN {% data variables.product.api_url_pre %}/user
```
you'll get a response that includes the `node_id` of the authenticated user:
diff --git a/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
index 3e15a0797b..0b598b4900 100644
--- a/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
+++ b/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -70,8 +70,8 @@ You can find the node ID of an organization project if you know the organization
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"query{organization(login: \"ORGANIZATION\") {projectV2(number: NUMBER){id}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"query{organization(login: \"ORGANIZATION\") {projectV2(number: NUMBER){id}}}"}'
```
{% endcurl %}
@@ -79,8 +79,8 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- organization(login: "ORGANIZATION"){
- projectV2(number: NUMBER) {
+ organization(login: "ORGANIZATION"){
+ projectV2(number: NUMBER) {
id
}
}
@@ -94,8 +94,8 @@ You can also find the node ID of all projects in your organization. The followin
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"{organization(login: \"ORGANIZATION\") {projectsV2(first: 20) {nodes {id title}}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"{organization(login: \"ORGANIZATION") {projectsV2(first: 20) {nodes {id title}}}}"}'
```
{% endcurl %}
@@ -103,7 +103,7 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- organization(login: "ORGANIZATION") {
+ organization(login: "ORGANIZATION") {
projectsV2(first: 20) {
nodes {
id
@@ -125,8 +125,8 @@ You can find the node ID of a user project if you know the project number. Repla
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"query{user(login: \"USER\") {projectV2(number: NUMBER){id}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"query{user(login: \"USER\") {projectV2(number: NUMBER){id}}}"}'
```
{% endcurl %}
@@ -134,8 +134,8 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- user(login: "USER"){
- projectV2(number: NUMBER) {
+ user(login: "USER"){
+ projectV2(number: NUMBER) {
id
}
}
@@ -149,8 +149,8 @@ You can also find the node ID for all of your projects. The following example wi
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"{user(login: \"USER\") {projectsV2(first: 20) {nodes {id title}}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"{user(login: \"USER\") {projectsV2(first: 20) {nodes {id title}}}}"}'
```
{% endcurl %}
@@ -158,7 +158,7 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- user(login: "USER") {
+ user(login: "USER") {
projectsV2(first: 20) {
nodes {
id
@@ -180,8 +180,8 @@ The following example will return the ID, name, settings, and configuration for
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
```
{% endcurl %}
@@ -189,7 +189,7 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- node(id: "PROJECT_ID") {
+ node(id: "PROJECT_ID") {
... on ProjectV2 {
fields(first: 20) {
nodes {
@@ -284,8 +284,8 @@ If you just need the name and ID of a field, and do not need information about i
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
```
{% endcurl %}
@@ -293,7 +293,7 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- node(id: "PROJECT_ID") {
+ node(id: "PROJECT_ID") {
... on ProjectV2 {
fields(first: 20) {
nodes {
@@ -354,8 +354,8 @@ The following example will return the first 20 issues, pull requests, and draft
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon { name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
```
{% endcurl %}
@@ -363,7 +363,7 @@ curl --request POST \
```shell
gh api graphql -f query='
query{
- node(id: "PROJECT_ID") {
+ node(id: "PROJECT_ID") {
... on ProjectV2 {
items(first: 20) {
nodes{
@@ -446,8 +446,8 @@ The following example will add an issue or pull request to your project. Replace
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"PROJECT_ID\" contentId: \"CONTENT_ID\"}) {item {id}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"PROJECT_ID\" contentId: \"CONTENT_ID\"}) {item {id}}}"}'
```
{% endcurl %}
@@ -455,7 +455,7 @@ curl --request POST \
```shell
gh api graphql -f query='
mutation {
- addProjectV2ItemById(input: {projectId: "PROJECT_ID" contentId: "CONTENT_ID"}) {
+ addProjectV2ItemById(input: {projectId: "PROJECT_ID" contentId: "CONTENT_ID"}) {
item {
id
}
@@ -488,8 +488,8 @@ The following example will add a draft issue to your project. Replace `PROJECT_I
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {projectItem {id}}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {projectItem {id}}}"}'
```
{% endcurl %}
@@ -497,7 +497,7 @@ curl --request POST \
```shell
gh api graphql -f query='
mutation {
- addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {
+ addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {
projectItem {
id
}
@@ -528,8 +528,8 @@ The following example will update your project's settings. Replace `PROJECT_ID`
```shell
curl --request POST \
--url https://api.github.com/graphql \
---header 'Authorization: Bearer TOKEN' \
---data '{"query":"mutation { updateProjectV2(input: { projectId: \"PROJECT_ID\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
+--header 'Authorization: Bearer TOKEN' \
+--data '{"query":"mutation { updateProjectV2(input: { projectId: \"PROJECT_ID\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
```
{% endcurl %}
@@ -539,7 +539,7 @@ gh api graphql -f query='
mutation {
updateProjectV2(
input: {
- projectId: "PROJECT_ID",
+ projectId: "PROJECT_ID",
title: "Project title",
public: false,
readme: "# Project README\n\nA long description",
@@ -565,8 +565,8 @@ The following example will update the value of a text field for an item. Replace
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { text: "Updated text" }}) { projectV2Item { id }}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { text: "Updated text" }}) { projectV2Item { id }}}"}'
```
{% endcurl %}
@@ -576,9 +576,9 @@ gh api graphql -f query='
mutation {
updateProjectV2ItemFieldValue(
input: {
- projectId: "PROJECT_ID"
- itemId: "ITEM_ID"
- fieldId: "FIELD_ID"
+ projectId: "PROJECT_ID"
+ itemId: "ITEM_ID"
+ fieldId: "FIELD_ID"
value: {
text: "Updated text"
}
@@ -619,8 +619,8 @@ The following example will update the value of a single select field for an item
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
```
{% endcurl %}
@@ -630,11 +630,11 @@ gh api graphql -f query='
mutation {
updateProjectV2ItemFieldValue(
input: {
- projectId: "PROJECT_ID"
- itemId: "ITEM_ID"
- fieldId: "FIELD_ID"
+ projectId: "PROJECT_ID"
+ itemId: "ITEM_ID"
+ fieldId: "FIELD_ID"
value: {
- singleSelectOptionId: "OPTION_ID"
+ singleSelectOptionId: "OPTION_ID"
}
}
) {
@@ -659,8 +659,8 @@ The following example will update the value of an iteration field for an item.
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: "PROJECT_ID" itemId: "ITEM_ID" fieldId: "FIELD_ID" value: { singleSelectOptionId: "OPTION_ID" }}) { projectV2Item { id }}}"}'
```
{% endcurl %}
@@ -670,11 +670,11 @@ gh api graphql -f query='
mutation {
updateProjectV2ItemFieldValue(
input: {
- projectId: "PROJECT_ID"
- itemId: "ITEM_ID"
- fieldId: "FIELD_ID"
+ projectId: "PROJECT_ID"
+ itemId: "ITEM_ID"
+ fieldId: "FIELD_ID"
value: {
- iterationId: "ITERATION_ID"
+ iterationId: "ITERATION_ID"
}
}
) {
@@ -694,8 +694,8 @@ The following example will delete an item from a project. Replace `PROJECT_ID` w
```shell
curl --request POST \
--url https://api.github.com/graphql \
- --header 'Authorization: Bearer TOKEN' \
- --data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\"}) {deletedItemId}}"}'
+ --header 'Authorization: Bearer TOKEN' \
+ --data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\"}) {deletedItemId}}"}'
```
{% endcurl %}
@@ -705,8 +705,8 @@ gh api graphql -f query='
mutation {
deleteProjectV2Item(
input: {
- projectId: "PROJECT_ID"
- itemId: "ITEM_ID"
+ projectId: "PROJECT_ID"
+ itemId: "ITEM_ID"
}
) {
deletedItemId
diff --git a/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
index cfd6821b28..846d43cd1c 100644
--- a/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
+++ b/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -50,7 +50,7 @@ People or teams who are mentioned in the issue will receive a notification letti
To transfer an issue, use the `gh issue transfer` subcommand. Replace the `issue` parameter with the number or URL of the issue. Replace the `{% ifversion ghes %}hostname/{% endif %}owner/repo` parameter with the {% ifversion ghes %}URL{% else %}name{% endif %} of the repository that you want to transfer the issue to, such as `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`.
```shell
-gh issue transfer issue {% ifversion ghes %}hostname/{% endif %}owner/repo
+gh issue transfer ISSUE {% ifversion ghes %}HOSTNAME/{% endif %}OWNER/REPO
```
{% endcli %}
diff --git a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index 4a6d44a2fa..c9ebf87a04 100644
--- a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -49,7 +49,7 @@ When you issue each certificate, you must include an extension that specifies wh
{% endnote %}
```shell
-$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub
+$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub
```
{% warning %}
@@ -61,11 +61,11 @@ $ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{%
To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_.
```shell
-$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub
+$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub
```
You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia.
```shell
-$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub
+$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub
```
diff --git a/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
index a31fe1399b..76524a2ce0 100644
--- a/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
+++ b/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -65,7 +65,7 @@ To verify a domain, you must have access to modify domain records with your doma
{% data reusables.organizations.add-dns-txt-record %}
1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output.
```shell
- $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
+ $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
```
1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
{% data reusables.organizations.continue-verifying-domain %}
diff --git a/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
index 938cf7933b..fcdeb9ed53 100644
--- a/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
+++ b/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -36,7 +36,7 @@ By connecting a repository to a package, the package landing page will show info
1. In your Dockerfile, add this line, replacing {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` with your details:
```shell
- LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO
+ LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO
```
For example, if you're the user `monalisa` and own `my-repo`, and {% data variables.product.product_location %} hostname is `github.companyname.com`, you would add this line to your Dockerfile:
```shell
diff --git a/content/packages/quickstart.md b/content/packages/quickstart.md
index 839256b3ce..367b54eb17 100644
--- a/content/packages/quickstart.md
+++ b/content/packages/quickstart.md
@@ -21,8 +21,8 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
2. Clone the repository to your local machine.
```shell
- $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
- $ cd YOUR-REPOSITORY
+ $ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
+ $ cd YOUR-REPOSITORY
```
3. Create an `index.js` file and add a basic alert to say "Hello world!"
{% raw %}
@@ -35,9 +35,9 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
```shell
$ npm init
...
- package name: @YOUR-USERNAME/YOUR-REPOSITORY
+ package name: @YOUR-USERNAME/YOUR-REPOSITORY
...
- test command: exit 0
+ test command: exit 0
...
```
{% endraw %}
@@ -89,7 +89,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
- Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
{% raw %}
```shell
- @YOUR-USERNAME:registry=https://npm.pkg.github.com
+ @YOUR-USERNAME:registry=https://npm.pkg.github.com
```
{% endraw %}
- Edit the `package.json` file and specify the `publishConfig` key:
@@ -104,7 +104,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
```shell
$ git add .github/workflows/release-package.yml
# Also add the file you created or edited in the previous step.
- $ git add .npmrc or package.json
+ $ git add .npmrc or package.json
$ git commit -m "workflow to publish package"
$ git push
```
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
index dc433c384c..86d916e35e 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -53,7 +53,7 @@ To keep your credentials secure, we recommend you save your personal access toke
{% ifversion fpt or ghec %}
{% raw %}
```shell
- $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin
+ $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin
```
{% endraw %}
{% endif %}
@@ -64,7 +64,7 @@ If your instance has subdomain isolation enabled:
{% endif %}
{% raw %}
```shell
- $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin
+ $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin
```
{% endraw %}
{% ifversion ghes %}
@@ -72,7 +72,7 @@ If your instance has subdomain isolation disabled:
{% raw %}
```shell
- $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin
+ $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin
```
{% endraw %}
{% endif %}
@@ -102,62 +102,62 @@ For more information, see "[Docker login](https://docs.docker.com/engine/referen
$ docker images
> < >
> REPOSITORY TAG IMAGE ID CREATED SIZE
- > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB
+ > IMAGE_NAME VERSION IMAGE_ID 4 weeks ago 1.11MB
```
2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *VERSION* with package version at build time.
{% ifversion fpt or ghec %}
```shell
- $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+ $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
```
{% else %}
{% ifversion ghes %}
If your instance has subdomain isolation enabled:
{% endif %}
```shell
- $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+ $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
- $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+ $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
```
{% endif %}
{% endif %}
3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.product.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
{% ifversion fpt or ghec %}
```shell
- $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
+ $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
```
{% else %}
{% ifversion ghes %}
If your instance has subdomain isolation enabled:
{% endif %}
```shell
- $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
+ $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
- $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
+ $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
```
{% endif %}
{% endif %}
4. Publish the image to {% data variables.product.prodname_registry %}.
{% ifversion fpt or ghec %}
```shell
- $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+ $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
```
{% else %}
{% ifversion ghes %}
If your instance has subdomain isolation enabled:
{% endif %}
```shell
- $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+ $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
- $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+ $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
```
{% endif %}
{% endif %}
@@ -198,10 +198,10 @@ $ docker images
> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB
# Tag the image with OWNER/REPO/IMAGE_NAME
-$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0
+$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0
# Push the image to {% data variables.product.prodname_registry %}
-$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
+$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
```
{% endif %}
@@ -222,10 +222,10 @@ $ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
```shell
# Build the image with docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
# Assumes Dockerfile resides in the current working directory (.)
-$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 .
+$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 .
# Push the image to {% data variables.product.prodname_registry %}
-$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
+$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
```
{% endif %}
@@ -237,7 +237,7 @@ You can use the `docker pull` command to install a docker image from {% data var
{% ifversion fpt or ghec %}
```shell
-$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
+$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
```
{% else %}
@@ -245,12 +245,12 @@ $ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAMEHOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
+$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
-$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
+$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
```
{% endif %}
{% endif %}
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
index 7ff16231a5..dc5f62a139 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -57,10 +57,10 @@ publishing {
repositories {
maven {
name = "GitHubPackages"
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
- username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
- password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
+ username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
+ password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
}
}
}
@@ -84,10 +84,10 @@ subprojects {
repositories {
maven {
name = "GitHubPackages"
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
- username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
- password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
+ username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
+ password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
}
}
}
@@ -110,10 +110,10 @@ publishing {
repositories {
maven {
name = "GitHubPackages"
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
- username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
- password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
+ username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
+ password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
}
}
}
@@ -137,10 +137,10 @@ subprojects {
repositories {
maven {
name = "GitHubPackages"
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
- username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
- password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
+ username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
+ password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
}
}
}
@@ -192,10 +192,10 @@ To use a published package from {% data variables.product.prodname_registry %},
```shell
repositories {
maven {
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else % REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
- username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
- password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
+ username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
+ password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
}
}
}
@@ -204,10 +204,10 @@ To use a published package from {% data variables.product.prodname_registry %},
```shell
repositories {
maven {
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
- username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
- password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
+ username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
+ password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
}
}
}
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
index 8007cd2b6f..cc0d74151d 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -55,14 +55,14 @@ If your instance has subdomain isolation enabled:
{% endif %}
```shell
-//{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN
+//{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
-//HOSTNAME/_registry/npm/:_authToken=TOKEN
+//HOSTNAME/_registry/npm/:_authToken=TOKEN
```
{% endif %}
@@ -75,21 +75,21 @@ If your instance has subdomain isolation enabled:
{% endif %}
```shell
-$ npm login --scope=@OWNER --registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}
+$ npm login --scope=@OWNER --registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}
-> Username: USERNAME
-> Password: TOKEN
-> Email: PUBLIC-EMAIL-ADDRESS
+> Username: USERNAME
+> Password: TOKEN
+> Email: PUBLIC-EMAIL-ADDRESS
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
-$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/
-> Username: USERNAME
-> Password: TOKEN
-> Email: PUBLIC-EMAIL-ADDRESS
+$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/
+> Username: USERNAME
+> Password: TOKEN
+> Email: PUBLIC-EMAIL-ADDRESS
```
{% endif %}
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
{% endif %}
```shell
"publishConfig": {
- "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+ "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
},
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
"publishConfig": {
- "registry":"https://HOSTNAME/_registry/npm/"
+ "registry":"https://HOSTNAME/_registry/npm/"
},
```
{% endif %}
@@ -165,7 +165,7 @@ To ensure the repository's URL is correct, replace REPOSITORY with the name of t
{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name.
```shell
-"repository":"https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY",
+"repository":"https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY",
```
## Installing a package
@@ -213,16 +213,16 @@ If your instance has subdomain isolation enabled:
{% endif %}
```shell
-@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}
-@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}
+@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}
+@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}
```
{% ifversion ghes %}
If your instance has subdomain isolation disabled:
```shell
-@OWNER:registry=https://HOSTNAME/_registry/npm
-@OWNER:registry=https://HOSTNAME/_registry/npm
+@OWNER:registry=https://HOSTNAME/_registry/npm
+@OWNER:registry=https://HOSTNAME/_registry/npm
```
{% endif %}
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
index fc4326ab48..2693ca8d8b 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -106,7 +106,7 @@ If you don't already have a PAT to use for your account on {% ifversion ghae %}{
3. Publish the package using your PAT as the API key.
```shell
- dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github"
+ dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --api-key YOUR_GITHUB_PAT --source "github"
```
{% data reusables.package_registry.viewing-packages %}
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
index 22800bd5c6..533df4844e 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -60,7 +60,7 @@ For example, you would create or edit a *~/.gem/credentials* to include the foll
```shell
---
-:github: Bearer TOKEN
+:github: Bearer TOKEN
```
To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace:
@@ -89,7 +89,7 @@ If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this exa
To authenticate with Bundler, configure Bundler to use your personal access token, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your personal access token, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's RubyGems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.product.product_location %}.{% endif %}
```shell
-$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN
+$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN
```
## Publishing a package
@@ -107,8 +107,8 @@ $ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% els
```shell
$ gem push --key github \
- --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \
- OCTO-GEM-0.0.1.gem
+ --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \
+ OCTO-GEM-0.0.1.gem
```
## Publishing multiple packages to the same repository
diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
index 05e0b384b9..ff6270317a 100644
--- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
+++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -53,11 +53,11 @@ To set up a `www` or custom subdomain, such as `www.example.com` or `blog.exampl
{% data reusables.command_line.open_the_multi_os_terminal %}
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
```shell
- $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
- > ;WWW.EXAMPLE.COM. IN A
- > WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
- > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER .
- > GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1
+ $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
+ > ;WWW.EXAMPLE.COM. IN A
+ > WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
+ > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER .
+ > GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1
```
{% data reusables.pages.build-locally-download-cname %}
{% data reusables.pages.enforce-https-custom-domain %}
@@ -95,19 +95,19 @@ To set up an apex domain, such as `example.com`, you must configure a custom dom
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
- For `A` records.
```shell
- $ dig EXAMPLE.COM +noall +answer -t A
- > EXAMPLE.COM 3600 IN A 185.199.108.153
- > EXAMPLE.COM 3600 IN A 185.199.109.153
- > EXAMPLE.COM 3600 IN A 185.199.110.153
- > EXAMPLE.COM 3600 IN A 185.199.111.153
+ $ dig EXAMPLE.COM +noall +answer -t A
+ > EXAMPLE.COM 3600 IN A 185.199.108.153
+ > EXAMPLE.COM 3600 IN A 185.199.109.153
+ > EXAMPLE.COM 3600 IN A 185.199.110.153
+ > EXAMPLE.COM 3600 IN A 185.199.111.153
```
- For `AAAA` records.
```shell
- $ dig EXAMPLE.COM +noall +answer -t AAAA
- > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8000::153
- > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8001::153
- > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8002::153
- > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8003::153
+ $ dig EXAMPLE.COM +noall +answer -t AAAA
+ > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8000::153
+ > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8001::153
+ > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8002::153
+ > EXAMPLE.COM 3600 IN AAAA 2606:50c0:8003::153
```
{% data reusables.pages.build-locally-download-cname %}
{% data reusables.pages.enforce-https-custom-domain %}
@@ -123,11 +123,11 @@ After you configure the apex domain, you must configure a CNAME record with your
1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `.github.io` or `.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
```shell
- $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
- > ;WWW.EXAMPLE.COM. IN A
- > WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
- > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER .
- > GITHUB-PAGES-SERVER . 22 IN A 192.0.2.1
+ $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
+ > ;WWW.EXAMPLE.COM IN A
+ > WWW.EXAMPLE.COM. 3592 IN CNAME YOUR-USERNAME.github.io.
+ > YOUR-USERNAME.github.io. 43192 IN CNAME GITHUB-PAGES-SERVER.
+ > GITHUB-PAGES-SERVER. 22 IN A 192.0.2.1
```
## Removing a custom domain
diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
index d651bc8152..1cc2c09500 100644
--- a/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
+++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
@@ -39,8 +39,8 @@ Your theme includes default layouts, includes, and stylesheets that will automat
4. Add the following YAML frontmatter to the top of the file, replacing _PAGE TITLE_ with the page's title and _URL-PATH_ with a path you want for the page's URL. For example, if the base URL of your site is `https://octocat.github.io` and your _URL-PATH_ is `/about/contact/`, your page will be located at `https://octocat.github.io/about/contact`.
```shell
layout: page
- title: "PAGE TITLE"
- permalink: /URL-PATH/
+ title: "PAGE-TITLE"
+ permalink: /URL-PATH
```
5. Below the frontmatter, add content for your page.
{% data reusables.files.write_commit_message %}
@@ -62,9 +62,9 @@ Your theme includes default layouts, includes, and stylesheets that will automat
4. Add the following YAML frontmatter to the top of the file, replacing _POST TITLE_ with the post's title, _YYYY-MM-DD hh:mm:ss -0000_ with the date and time for the post, and _CATEGORY-1_ and _CATEGORY-2_ with as many categories you want for your post.
```shell
layout: post
- title: "POST TITLE"
- date: YYYY-MM-DD hh:mm:ss -0000
- categories: CATEGORY-1 CATEGORY-2
+ title: "POST-TITLE"
+ date: YYYY-MM-DD hh:mm:ss -0000
+ categories: CATEGORY-1 CATEGORY-2
```
5. Below the frontmatter, add content for your post.
{% data reusables.files.write_commit_message %}
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 925365fc4d..685799724c 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
@@ -45,17 +45,17 @@ Before you can use Jekyll to create a {% data variables.product.prodname_pages %
{% data reusables.command_line.open_the_multi_os_terminal %}
1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
```shell
- $ cd PARENT-FOLDER
+ $ cd PARENT-FOLDER
```
1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository.
```shell
- $ git init REPOSITORY-NAME
+ $ git init REPOSITORY-NAME
> Initialized empty Git repository in /Users/octocat/my-site/.git/
# Creates a new folder on your computer, initialized as a Git repository
```
4. Change directories to the repository.
```shell
- $ cd REPOSITORY-NAME
+ $ cd REPOSITORY-NAME
# Changes the working directory
```
{% data reusables.pages.decide-publishing-source %}
@@ -106,14 +106,14 @@ git commit -m 'Initial GitHub pages site with Jekyll'
1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository.
```shell
{% ifversion fpt or ghec %}
-$ git remote add origin https://github.com/USER/REPOSITORY.git
+$ git remote add origin https://github.com/USER/REPOSITORY.git
{% else %}
-$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git
+$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git
{% endif %}
```
1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on.
```shell
- $ git push -u origin BRANCH
+ $ git push -u origin BRANCH
```
{% data reusables.pages.configure-publishing-source %}
{% data reusables.pages.navigate-site-repo %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md b/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
index 46fd83c6c2..10630f1a54 100644
--- a/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
+++ b/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
@@ -30,7 +30,7 @@ To resolve a merge conflict, you must manually edit the conflicted file to selec
If you have a merge conflict on the command line, you cannot push your local changes to {% data variables.product.product_name %} until you resolve the merge conflict locally on your computer. If you try merging branches on the command line that have a merge conflict, you'll get an error message. For more information, see "[Resolving a merge conflict using the command line](/articles/resolving-a-merge-conflict-using-the-command-line/)."
```shell
-$ git merge BRANCH-NAME
+$ git merge BRANCH-NAME
> Auto-merging styleguide.md
> CONFLICT (content): Merge conflict in styleguide.md
> Automatic merge failed; fix conflicts and then commit the result
diff --git a/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
index 7354246bea..dbd648bfc3 100644
--- a/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
+++ b/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
@@ -33,7 +33,7 @@ For example, if you and another person both edited the file _styleguide.md_ on t
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Navigate into the local Git repository that has the merge conflict.
```shell
- cd REPOSITORY-NAME
+ cd REPOSITORY-NAME
```
3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
```shell
@@ -85,7 +85,7 @@ For example, if you edited a file, such as *README.md*, and another person remov
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Navigate into the local Git repository that has the merge conflict.
```shell
- cd REPOSITORY-NAME
+ cd REPOSITORY-NAME
```
2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
```shell
diff --git a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
index 881c4b1c19..6b0e4a5418 100644
--- a/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
+++ b/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -83,7 +83,7 @@ If you decide you don't want the changes in a topic branch to be merged to the u
To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
```shell
-gh pr merge pull-request
+gh pr merge PULL-REQUEST
```
Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
index 6dc332b6d9..0480d3a39c 100644
--- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
+++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -43,11 +43,11 @@ Only the user who created the pull request can give you permission to push commi
```
5. Type `git clone`, and then paste the URL you copied in Step 3.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
+ $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
```
6. Press **Enter**. Your local clone will be created.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
+ $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
> Cloning into `FORK-OF-THE-REPOSITORY`...
> remote: Counting objects: 10, done.
> remote: Compressing objects: 100% (8/8), done.
@@ -61,13 +61,13 @@ Only the user who created the pull request can give you permission to push commi
{% endtip %}
7. Navigate into your new cloned repository.
```shell
- $ cd FORK-OF-THE-REPOSITORY
+ $ cd FORK-OF-THE-REPOSITORY
```
7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.
In this example, the compare branch is `test-branch`:
```shell
- $ git checkout test-branch
+ $ git checkout TEST-BRANCH
```
{% tip %}
@@ -84,8 +84,8 @@ Only the user who created the pull request can give you permission to push commi
> Compressing objects: 100% (26/26), done.
> Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
> Total 29 (delta 8), reused 0 (delta 0)
- > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git
- > 12da2e9..250e946 test-branch -> test-branch
+ > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git
+ > 12da2e9..250e946 TEST-BRANCH -> TEST-BRANCH
```
Your new commits will be reflected on the original pull request on {% data variables.product.product_location %}.
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index cbfc7e4cab..a2f42020f0 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -44,7 +44,7 @@ shortTitle: Check out a PR locally
To check out a pull request locally, use the `gh pr checkout` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
```shell
-gh pr checkout pull-request
+gh pr checkout PULL-REQUEST
```
{% endcli %}
@@ -64,24 +64,24 @@ Anyone can work with a previously opened pull request to continue working on it,
{% data reusables.command_line.open_the_multi_os_terminal %}
5. Fetch the reference to the pull request based on its ID number, creating a new branch in the process.
```shell
- $ git fetch origin pull/ID/head:BRANCHNAME
+ $ git fetch origin pull/ID/head:BRANCH_NAME
```
6. Switch to the new branch that's based on this pull request:
```shell
- [main] $ git checkout BRANCHNAME
- > Switched to a new branch 'BRANCHNAME'
+ [main] $ git checkout BRANCH_NAME
+ > Switched to a new branch 'BRANCH_NAME'
```
7. At this point, you can do anything you want with this branch. You can run some local tests, or merge other branches into the branch.
8. When you're ready, you can push the new branch up:
```shell
- [pull-inactive-pull-request] $ git push origin BRANCHNAME
+ [pull-inactive-pull-request] $ git push origin BRANCHNAME
> Counting objects: 32, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (26/26), done.
> Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
> Total 29 (delta 8), reused 0 (delta 0)
- > To https://{% data variables.command_line.codeblock %}/username/repository.git
- > * [new branch] BRANCHNAME -> BRANCHNAME
+ > To https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
+ > * [new branch] BRANCH_NAME -> BRANCH_NAME
```
9. [Create a new pull request](/articles/creating-a-pull-request) with your new branch.
@@ -90,7 +90,7 @@ Anyone can work with a previously opened pull request to continue working on it,
The remote `refs/pull/` namespace is *read-only*. If you try to push any commits there, you'll see this error:
```shell
! [remote rejected] HEAD -> refs/pull/1/head (deny updating a hidden ref)
-error: failed to push some refs to 'git@github.local:USERNAME/REPOSITORY.git'
+error: failed to push some refs to 'git@github.local:USERNAME/REPOSITORY.git'
```
{% tip %}
diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
index 38e4a7e7d4..00882c58ed 100644
--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
@@ -19,18 +19,18 @@ shortTitle: Configure a remote
2. List the current configured remote repository for your fork.
```shell
$ git remote -v
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
```
3. Specify a new remote *upstream* repository that will be synced with the fork.
```shell
- $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git
+ $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git
```
4. Verify the new upstream repository you've specified for your fork.
```shell
$ git remote -v
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
- > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
- > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch)
- > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (fetch)
+ > origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_FORK.git (push)
+ > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch)
+ > upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push)
```
diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index b1b70872ec..4916aeb3cd 100644
--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -45,7 +45,7 @@ If the changes from the upstream repository cause conflicts, {% data variables.p
To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments.
```shell
-$ gh repo sync owner/cli-fork -b BRANCHNAME
+$ gh repo sync owner/cli-fork -b BRANCH_NAME
```
If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch.
@@ -64,7 +64,7 @@ Before you can sync your fork with an upstream repository, you must [configure a
> remote: Compressing objects: 100% (53/53), done.
> remote: Total 62 (delta 27), reused 44 (delta 9)
> Unpacking objects: 100% (62/62), done.
- > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
+ > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
> * [new branch] main -> upstream/main
```
diff --git a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
index 520fd34daa..aade27112e 100644
--- a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
+++ b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -53,7 +53,7 @@ We strongly discourage force pushing, since this changes the history of your rep
1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message.
2. Use the `push --force-with-lease` command to force push over the old commit.
```shell
- $ git push --force-with-lease origin example-branch
+ $ git push --force-with-lease origin EXAMPLE-BRANCH
```
**Changing the message of older or multiple commit messages**
@@ -102,7 +102,7 @@ If you need to amend the message for multiple commits or an older commit, you ca
5. In each resulting commit file, type the new commit message, save the file, and close it.
6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit.
```shell
-$ git push --force origin example-branch
+$ git push --force origin EXAMPLE-BRANCH
```
For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual.
diff --git a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
index a7082678b8..e25a47c844 100644
--- a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
+++ b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
@@ -47,7 +47,7 @@ Organizations can use the `name@organization.com` email as a public point of con
$ git commit -m "Refactor usability tests.
>
>
- on-behalf-of: @org <name@organization.com>"
+ on-behalf-of: @ORG NAME@ORGANIZATION.COM"
```
The new commit, message, and badge will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)."
diff --git a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
index 75eca09a64..97444af18d 100644
--- a/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
+++ b/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
@@ -61,8 +61,8 @@ You can use {% data variables.product.prodname_desktop %} to create a commit wit
$ git commit -m "Refactor usability tests.
>
>
- Co-authored-by: name <name@example.com>
- Co-authored-by: another-name <another-name@example.com>"
+ Co-authored-by: NAME NAME@EXAMPLE.COM
+ Co-authored-by: AUTHOR-NAME ANOTHER-NAME@EXAMPLE.COM"
```
The new commit and message will appear on {% data variables.product.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)."
diff --git a/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
index 613caee543..24834a7df7 100644
--- a/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
+++ b/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
@@ -36,7 +36,7 @@ There are several possible explanations:
Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`:
```shell
-$ git fetch remote
+$ git fetch REMOTE
```
This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out.
diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
index 1abc2a6e87..5ec69c8950 100644
--- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
+++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -41,9 +41,9 @@ After you rename a branch in a repository on {% data variables.product.product_n
From the local clone of the repository on a computer, run the following commands to update the name of the default branch.
```shell
-$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME
+$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME
$ git fetch origin
-$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME
+$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME
$ git remote set-head origin -a
```
diff --git a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index 0fb1ff7c56..c8bf281fc9 100644
--- a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -42,14 +42,15 @@ You can clone your existing repository or clone another person's existing reposi
To clone a repository locally, use the `repo clone` subcommand. Replace the `repository` parameter with the repository name. For example, `octo-org/octo-repo`, `monalisa/octo-repo`, or `octo-repo`. If the `OWNER/` portion of the `OWNER/REPO` repository argument is omitted, it defaults to the name of the authenticating user.
```shell
-gh repo clone repository
+gh repo clone REPOSITORY
```
You can also use the GitHub URL to clone a repository.
```shell
-gh repo clone https://github.com/cli/cli
+gh repo clone URL
```
+Replace URL with the URL of a GitHub repository. For example, `https://github.com/cli/cli`
{% endcli %}
diff --git a/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
index 133488a738..ea41e01734 100644
--- a/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
@@ -31,17 +31,17 @@ Before you can push the original repository to your new copy, or _mirror_, of th
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Create a bare clone of the repository.
```shell
- $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git
+ $ git clone --bare https://{% data variables.command_line.codeblock %}/OLD-REPOSITORY.git/OLD-REPOSITORY.git
```
3. Mirror-push to the new repository.
```shell
- $ cd old-repository.git
- $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git
+ $ cd OLD-REPOSITORY.git
+ $ git push --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/NEW-REPOSITORY.git
```
4. Remove the temporary local repository you created earlier.
```shell
$ cd ..
- $ rm -rf old-repository.git
+ $ rm -rf OLD-REPOSITORY.git
```
## Mirroring a repository that contains {% data variables.large_files.product_name_long %} objects
@@ -49,11 +49,11 @@ Before you can push the original repository to your new copy, or _mirror_, of th
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Create a bare clone of the repository. Replace the example username with the name of the person or organization who owns the repository, and replace the example repository name with the name of the repository you'd like to duplicate.
```shell
- $ git clone --bare https://{% data variables.command_line.codeblock %}/exampleuser/old-repository.git
+ $ git clone --bare https://{% data variables.command_line.codeblock %}/OLD-REPOSITORY.git/OLD-REPOSITORY.git
```
3. Navigate to the repository you just cloned.
```shell
- $ cd old-repository.git
+ $ cd OLD-REPOSITORY.git
```
4. Pull in the repository's {% data variables.large_files.product_name_long %} objects.
```shell
@@ -61,16 +61,16 @@ Before you can push the original repository to your new copy, or _mirror_, of th
```
5. Mirror-push to the new repository.
```shell
- $ git push --mirror https://{% data variables.command_line.codeblock %}/exampleuser/new-repository.git
+ $ git push --mirror https://{% data variables.command_line.codeblock %}/OLD-REPOSITORY.git/NEW-REPOSITORY.git
```
6. Push the repository's {% data variables.large_files.product_name_long %} objects to your mirror.
```shell
- $ git lfs push --all https://github.com/exampleuser/new-repository.git
+ $ git lfs push --all https://github.com/EXAMPLE-USER/NEW-REPOSITORY.git
```
7. Remove the temporary local repository you created earlier.
```shell
$ cd ..
- $ rm -rf old-repository.git
+ $ rm -rf OLD-REPOSITORY.git
```
## Mirroring a repository in another location
@@ -80,12 +80,12 @@ If you want to mirror a repository in another location, including getting update
{% data reusables.command_line.open_the_multi_os_terminal %}
2. Create a bare mirrored clone of the repository.
```shell
- $ git clone --mirror https://{% data variables.command_line.codeblock %}/exampleuser/repository-to-mirror.git
+ $ git clone --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/REPOSITORY-TO-MIRROR.git
```
3. Set the push location to your mirror.
```shell
- $ cd repository-to-mirror
- $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/exampleuser/mirrored
+ $ cd REPOSITORY-TO-MIRROR
+ $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/MIRRORED
```
As with a bare clone, a mirrored clone includes all remote branches and tags, but all local references will be overwritten each time you fetch, so it will always be the same as the original repository. Setting the URL for pushes simplifies pushing to your mirror.
diff --git a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
index 7d86a30d4d..0d3f8b8abf 100644
--- a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@@ -25,7 +25,7 @@ For more information on project sites, see "[About {% data variables.product.pro
In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
```shell
-$ git remote set-url origin new_url
+$ git remote set-url origin NEW_URL
```
For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
diff --git a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index 74666a44c8..f005ae776d 100644
--- a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -48,7 +48,7 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
```shell
- $ git remote set-url origin new_url
+ $ git remote set-url origin NEW_URL
```
- When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
diff --git a/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
index 4f8d39702e..9d85d13f7f 100644
--- a/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
+++ b/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
@@ -29,18 +29,18 @@ Here's an example of an HTTPS error you might receive:
```shell
> error: The requested URL returned error: 401 while accessing
-> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs?service=git-receive-pack
+> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs?service=git-receive-pack
> fatal: HTTP request failed
```
```shell
> Error: The requested URL returned error: 403 while accessing
-> https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs
+> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs
> fatal: HTTP request failed
```
```shell
-> Error: https://{% data variables.command_line.codeblock %}/user/repo.git/info/refs not found: did you run git
+> Error: https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs not found: did you run git
> update-server-info on the server?
```
@@ -124,7 +124,7 @@ the following into the command line:
```shell
$ ssh -T git@{% data variables.command_line.codeblock %}
-> Hi username! You've successfully authenticated, but GitHub does not
+> Hi USERNAME! You've successfully authenticated, but GitHub does not
> provide shell access.
```
@@ -152,7 +152,7 @@ This error occurs if the default branch of a repository has been deleted on {% d
Detecting this error is simple; Git will warn you when you try to clone the repository:
```shell
-$ git clone https://{% data variables.command_line.codeblock %}/user/repo.git
+$ git clone https://{% data variables.command_line.codeblock %}/USER/REPO.git
# Clone a repo
> Cloning into 'repo'...
> remote: Counting objects: 66179, done.
diff --git a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index 3c3716db6f..5e3d777840 100644
--- a/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -90,7 +90,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release.
```shell
- gh release create tag
+ gh release create TAG
```
2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
@@ -153,7 +153,7 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation.
```shell
- gh release delete tag -y
+ gh release delete TAG -y
```
{% endcli %}
diff --git a/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md b/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
index fc6581d184..8f0f3eca5c 100644
--- a/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
+++ b/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
@@ -55,17 +55,17 @@ Many files can be [moved directly on {% data variables.product.product_name %}](
3. Use `git status` to check the old and new file locations.
```shell
$ git status
- > # On branch your-branch
+ > # On branch YOUR-BRANCH
> # Changes not staged for commit:
> # (use "git add/rm ..." to update what will be committed)
> # (use "git checkout -- ..." to discard changes in working directory)
> #
- > # deleted: /old-folder/image.png
+ > # deleted: /OLD-FOLDER/IMAGE.PNG
> #
> # Untracked files:
> # (use "git add ..." to include in what will be committed)
> #
- > # /new-folder/image.png
+ > # /NEW-FOLDER/IMAGE.PNG
> #
> # no changes added to commit (use "git add" and/or "git commit -a")
```
@@ -78,7 +78,7 @@ Many files can be [moved directly on {% data variables.product.product_name %}](
5. Use `git status` to check the changes staged for commit.
```shell
$ git status
- > # On branch your-branch
+ > # On branch YOUR-BRANCH
> # Changes to be committed:
> # (use "git reset HEAD ..." to unstage)
> #
diff --git a/content/repositories/working-with-files/managing-files/renaming-a-file.md b/content/repositories/working-with-files/managing-files/renaming-a-file.md
index 66bf319c27..03b7e8130f 100644
--- a/content/repositories/working-with-files/managing-files/renaming-a-file.md
+++ b/content/repositories/working-with-files/managing-files/renaming-a-file.md
@@ -52,16 +52,16 @@ Many files can be [renamed directly on {% data variables.product.product_name %}
{% data reusables.command_line.switching_directories_procedural %}
3. Rename the file, specifying the old file name and the new name you'd like to give the file. This will stage your change for commit.
```shell
- $ git mv old_filename new_filename
+ $ git mv OLD-FILENAME NEW-FILENAME
```
4. Use `git status` to check the old and new file names.
```shell
$ git status
- > # On branch your-branch
+ > # On branch YOUR-BRANCH
> # Changes to be committed:
> # (use "git reset HEAD ..." to unstage)
> #
- > # renamed: old_filename -> new_filename
+ > # renamed: OLD-FILENAME -> NEW-FILENAME
> #
```
{% data reusables.git.commit-file %}
diff --git a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
index 02fbcd36ad..ff023cdbc8 100644
--- a/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
+++ b/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
@@ -74,7 +74,7 @@ If the file was added with your most recent commit, and you have not pushed to {
{% data reusables.command_line.switching_directories_procedural %}
3. To remove the file, enter `git rm --cached`:
```shell
- $ git rm --cached giant_file
+ $ git rm --cached GIANT_FILE
# Stage our giant file for removal, but leave it on disk
```
4. Commit this change using `--amend -CHEAD`:
diff --git a/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
index 744ea932b5..91b7f2d948 100644
--- a/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
+++ b/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -25,7 +25,7 @@ shortTitle: Install Git LFS
{% data reusables.command_line.open_the_multi_os_terminal %}
3. Change the current working directory into the folder you downloaded and unzipped.
```shell
- $ cd ~/Downloads/git-lfs-1.X.X
+ $ cd ~/Downloads/git-lfs-1.X.X
```
{% note %}
@@ -85,7 +85,7 @@ shortTitle: Install Git LFS
{% data reusables.command_line.open_the_multi_os_terminal %}
3. Change the current working directory into the folder you downloaded and unzipped.
```shell
- $ cd ~/Downloads/git-lfs-1.X.X
+ $ cd ~/Downloads/git-lfs-1.X.X
```
{% note %}
diff --git a/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 412797926e..e5ed8d281d 100644
--- a/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -340,7 +340,7 @@ To view a fully interactive version of your Jupyter Notebook, you can set up a n
If you're having trouble rendering Jupyter Notebook files in static HTML, you can convert the file locally on the command line by using the [`nbconvert` command](https://github.com/jupyter/nbconvert):
```shell
-$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb
+$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb
```
### Further reading
diff --git a/content/rest/enterprise-admin/index.md b/content/rest/enterprise-admin/index.md
index 4221451d7a..3350cf559d 100644
--- a/content/rest/enterprise-admin/index.md
+++ b/content/rest/enterprise-admin/index.md
@@ -59,7 +59,7 @@ When endpoints include `{enterprise}`, replace `{enterprise}` with the handle fo
[Management Console](#management-console) API endpoints are only prefixed with a hostname:
```shell
-http(s)://hostname/
+http(s)://HOSTNAME/
```
{% endif %}
{% ifversion ghae or ghes %}
diff --git a/content/rest/enterprise-admin/management-console.md b/content/rest/enterprise-admin/management-console.md
index 83bb465f04..0f1095eb85 100644
--- a/content/rest/enterprise-admin/management-console.md
+++ b/content/rest/enterprise-admin/management-console.md
@@ -25,11 +25,11 @@ You need to pass your [Management Console password](/enterprise/admin/articles/a
Use the `api_key` parameter to send this token with each request. For example:
```shell
-$ curl -L 'https://hostname:admin_port/setup/api?api_key=your-amazing-password'
+$ curl -L 'https://HOSTNAME:ADMIN-PORT/setup/api?api_key=YOUR_AMAZING_PASSWORD'
```
You can also use standard HTTP authentication to send this token. For example:
```shell
-$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api'
+$ curl -L -u "api_key:YOUR_AMAZING_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api'
```
diff --git a/content/rest/guides/getting-started-with-the-rest-api.md b/content/rest/guides/getting-started-with-the-rest-api.md
index 8c54d89f60..880881e256 100644
--- a/content/rest/guides/getting-started-with-the-rest-api.md
+++ b/content/rest/guides/getting-started-with-the-rest-api.md
@@ -161,7 +161,7 @@ With cURL, you will send an `Authorization` header with your token. Replace `YOU
```shell
curl --request GET \
--url "https://api.github.com/octocat" \
---header "Authorization: Bearer YOUR-TOKEN"
+--header "Authorization: Bearer YOUR-TOKEN"
```
{% note %}
@@ -324,7 +324,7 @@ To send a header with cURL, use the `--header` or `-H` flag followed by the head
curl --request GET \
--url "https://api.github.com/octocat" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN"
+--header "Authorization: Bearer YOUR-TOKEN"
```
{% endcurl %}
@@ -388,7 +388,7 @@ To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN"
+--header "Authorization: Bearer YOUR-TOKEN"
```
{% endcurl %}
@@ -441,7 +441,7 @@ For cURL, add a `?` to the end of the path, then append your query parameter nam
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2&sort=updated&direction=asc" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN"
+--header "Authorization: Bearer YOUR-TOKEN"
```
{% endcurl %}
@@ -493,7 +493,7 @@ For cURL, use the `--data` flag to pass the body parameters in a JSON object.
curl --request POST \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN" \
+--header "Authorization: Bearer YOUR-TOKEN" \
--data '{
"title": "Created with the REST API",
"body": "This is a test issue created by the REST API"
@@ -591,7 +591,7 @@ For example, this request:
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN" \
+--header "Authorization: Bearer YOUR-TOKEN" \
--include
```
@@ -659,7 +659,7 @@ await octokit.request("GET /repos/{owner}/{repo}/issues", {
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN"
+--header "Authorization: Bearer YOUR-TOKEN"
```
{% endcurl %}
@@ -728,7 +728,7 @@ For example, you can use `>` to redirect the response to a file:
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
--header "Accept: application/vnd.github.v3+json" \
---header "Authorization: Bearer YOUR-TOKEN" > data.json
+--header "Authorization: Bearer YOUR-TOKEN" > data.json
```
Then you can use jq to get the title and author ID of each issue:
diff --git a/content/rest/overview/other-authentication-methods.md b/content/rest/overview/other-authentication-methods.md
index d8147fdb5d..9cebcf591a 100644
--- a/content/rest/overview/other-authentication-methods.md
+++ b/content/rest/overview/other-authentication-methods.md
@@ -45,7 +45,7 @@ response. The solution is to manually craft the `Authorization` header.
We recommend you use OAuth tokens to authenticate to the GitHub API. OAuth tokens include [personal access tokens][personal-access-tokens] and enable the user to revoke access at any time.
```shell
-$ curl -u username:token {% data variables.product.api_url_pre %}/user
+$ curl -u USERNAME:TOKEN {% data variables.product.api_url_pre %}/user
```
This approach is useful if your tools only support Basic Authentication but you want to take advantage of OAuth access token security features.
@@ -71,7 +71,7 @@ would authenticate you if you replace `` with your {% data variables.p
(cURL will prompt you to enter the password.)
```shell
-$ curl -u username {% data variables.product.api_url_pre %}/user
+$ curl -u USERNAME {% data variables.product.api_url_pre %}/user
```
If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
@@ -95,7 +95,7 @@ If you have two-factor authentication enabled, make sure you understand how to [
If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a personal access token (PAT) and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization.
```shell
-$ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test
+$ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test
> X-GitHub-SSO: required; url=https://github.com/orgs/octodocs-test/sso?authorization_request=AZSCKtL4U8yX1H3sCQIVnVgmjmon5fWxks5YrqhJgah0b2tlbl9pZM4EuMz4
{
@@ -107,7 +107,7 @@ $ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.ap
When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your personal access token:
```shell
-$ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/user/issues
+$ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/user/issues
> X-GitHub-SSO: partial-results; organizations=21955855,20582480
```
@@ -136,9 +136,9 @@ This header tells you how your account receives its two-factor authentication co
```shell
$ curl --request POST \
--url https://api.github.com/authorizations \
- --header 'authorization: Basic PASSWORD' \
+ --header 'authorization: Basic PASSWORD' \
--header 'content-type: application/json' \
- --header 'x-github-otp: OTP' \
+ --header 'x-github-otp: OTP' \
--data '{"scopes": ["public_repo"], "note": "test"}'
```
{% endif %}
diff --git a/content/rest/overview/resources-in-the-rest-api.md b/content/rest/overview/resources-in-the-rest-api.md
index 033f0ccd78..0432d216c9 100644
--- a/content/rest/overview/resources-in-the-rest-api.md
+++ b/content/rest/overview/resources-in-the-rest-api.md
@@ -91,7 +91,7 @@ $ curl -u "username" {% data variables.product.api_url_pre %}
### OAuth2 token (sent in a header)
```shell
-$ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}
+$ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}
```
{% note %}
@@ -150,7 +150,7 @@ the API will temporarily reject all authentication attempts for that user
```shell
$ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %}
--u valid_username:valid_token {% endif %}{% ifversion ghes %}-u valid_username:valid_password {% endif %}
+-u VALID_USERNAME:VALID_TOKEN {% endif %}{% ifversion ghes %}-u VALID_USERNAME:VALID_PASSWORD {% endif %}
> HTTP/2 403
> {
> "message": "Maximum number of login attempts exceeded. Please try again later.",
@@ -185,7 +185,7 @@ You can issue a `GET` request to the root endpoint to get all the endpoint categ
```shell
$ curl {% ifversion fpt or ghae or ghec %}
--u username:token {% endif %}{% ifversion ghes %}-u username:password {% endif %}{% data variables.product.api_url_pre %}
+-u USERNAME:TOKEN {% endif %}{% ifversion ghes %}-u USERNAME:PASSWORD {% endif %}{% data variables.product.api_url_pre %}
```
## GraphQL global node IDs
diff --git a/content/rest/quickstart.md b/content/rest/quickstart.md
index 7c56fcf402..e70d6f2272 100644
--- a/content/rest/quickstart.md
+++ b/content/rest/quickstart.md
@@ -279,7 +279,7 @@ jobs:
curl --request GET \
--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
--header "Accept: application/vnd.github.v3+json" \
- --header "Authorization: Bearer YOUR-TOKEN"
+ --header "Authorization: Bearer YOUR-TOKEN"
```
{% note %}
diff --git a/content/support/contacting-github-support/providing-data-to-github-support.md b/content/support/contacting-github-support/providing-data-to-github-support.md
index c2966bf474..7e3c1432ec 100644
--- a/content/support/contacting-github-support/providing-data-to-github-support.md
+++ b/content/support/contacting-github-support/providing-data-to-github-support.md
@@ -71,7 +71,7 @@ You can use this method without signing into the {% data variables.enterprise.ma
Use the [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance.
```shell
-$ ssh -p122 admin@hostname -- 'ghe-diagnostics' > diagnostics.txt
+$ ssh -p122 admin@HOSTNAME -- 'ghe-diagnostics' > diagnostics.txt
```
## Creating and sharing support bundles
@@ -119,7 +119,7 @@ You can use these steps to create and share a support bundle if you have SSH acc
1. Download the support bundle via SSH:
```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
```
For more information about the `ghe-support-bundle` command, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)".
{% data reusables.enterprise_enterprise_support.sign-in-to-support %}
@@ -147,7 +147,7 @@ You can directly upload a support bundle to our server if:
1. Upload the bundle to our support bundle server:
```shell
- $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u'
+ $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u'
```
## Creating and sharing extended support bundles
@@ -162,7 +162,7 @@ You can use these steps to create and share an extended support bundle if you ha
1. Download the extended support bundle via SSH by adding the `-x` flag to the `ghe-support-bundle` command:
```shell
- $ ssh -p 122 admin@hostname -- 'ghe-support-bundle -o -x' > support-bundle.tgz
+ $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o -x' > support-bundle.tgz
```
{% data reusables.enterprise_enterprise_support.sign-in-to-support %}
{% data reusables.enterprise_enterprise_support.upload-support-bundle %}
@@ -175,7 +175,7 @@ You can directly upload a support bundle to our server if:
1. Upload the bundle to our support bundle server:
```shell
- $ ssh -p122 admin@hostname -- 'ghe-support-bundle -u -x'
+ $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u -x'
```
## Further reading
diff --git a/contributing/content-markup-reference.md b/contributing/content-markup-reference.md
index c6408fe9b4..bdb4f828a8 100644
--- a/contributing/content-markup-reference.md
+++ b/contributing/content-markup-reference.md
@@ -67,7 +67,7 @@ To render syntax highlighting in command line instructions, we use triple backti
### Usage
```shell
- git init YOUR_REPO
+ git init YOUR_REPO
```
This syntax highlighting renders light text on a dark background, and should be reserved for command line instructions.
diff --git a/data/reusables/actions/self-hosted-runner-check-mac-linux.md b/data/reusables/actions/self-hosted-runner-check-mac-linux.md
index 34fab292bc..5a946bfa75 100644
--- a/data/reusables/actions/self-hosted-runner-check-mac-linux.md
+++ b/data/reusables/actions/self-hosted-runner-check-mac-linux.md
@@ -1,3 +1,4 @@
```shell
-./run.sh --check --url https://github.com/octo-org/octo-repo --pat ghp_abcd1234
+./run.sh --check --url URL --pat ghp_abcd1234
```
+Replace URL with the URL of repository. For example, `https://github.com/octo-org/octo-repo`.
\ No newline at end of file
diff --git a/data/reusables/command_line/git-clone-url.md b/data/reusables/command_line/git-clone-url.md
index 0ed7dd6815..7f2210364a 100644
--- a/data/reusables/command_line/git-clone-url.md
+++ b/data/reusables/command_line/git-clone-url.md
@@ -1,4 +1,4 @@
5. Type `git clone`, and then paste the URL you copied earlier.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
+ $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
```
diff --git a/data/reusables/command_line/local-clone-created.md b/data/reusables/command_line/local-clone-created.md
index 1fa36e1964..de216eff20 100644
--- a/data/reusables/command_line/local-clone-created.md
+++ b/data/reusables/command_line/local-clone-created.md
@@ -1,6 +1,6 @@
6. Press **Enter** to create your local clone.
```shell
- $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
+ $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
> Cloning into `Spoon-Knife`...
> remote: Counting objects: 10, done.
> remote: Compressing objects: 100% (8/8), done.
diff --git a/data/reusables/command_line/providing-token-as-password.md b/data/reusables/command_line/providing-token-as-password.md
index a938fcfd9c..44e5a96cae 100644
--- a/data/reusables/command_line/providing-token-as-password.md
+++ b/data/reusables/command_line/providing-token-as-password.md
@@ -3,7 +3,7 @@ Once you have a token, you can enter it instead of your password when performing
For example, on the command line you would enter the following:
```shell
-$ git clone https://{% data variables.command_line.codeblock %}/username/repo.git
-Username: your_username
-Password: your_token
+$ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPO.git
+Username: YOUR_USERNAME
+Password: YOUR_TOKEN
```
diff --git a/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md b/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md
index 8d44dbb727..3465598ef8 100644
--- a/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md
+++ b/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md
@@ -1,7 +1,7 @@
When rolling back an upgrade, you must use an upgrade package file with the *.pkg* extension. Hotpatch package files with the *.hpkg* extension are not supported.
```shell
-ghe-upgrade --allow-patch-rollback EARLIER-RELEASE-UPGRADE-PACKAGE.pkg
+ghe-upgrade --allow-patch-rollback EARLIER-RELEASE-UPGRADE-PACKAGE.pkg
```
A reboot is required after running the command. Rolling back does not affect the data partition, as migrations are not run on patch releases.
diff --git a/data/reusables/enterprise_installation/configuration-recognized.md b/data/reusables/enterprise_installation/configuration-recognized.md
index 60d20391dc..4cb2268a49 100644
--- a/data/reusables/enterprise_installation/configuration-recognized.md
+++ b/data/reusables/enterprise_installation/configuration-recognized.md
@@ -1,5 +1,5 @@
1. Once the instance has fully restarted and you can reach it, use the SSH administrative shell to verify that the new resource configuration is recognized:
```shell
-$ ssh -p 122 admin@HOSTNAME
+$ ssh -p 122 admin@HOSTNAME
$ ghe-system-info
```
diff --git a/data/reusables/enterprise_installation/download-package.md b/data/reusables/enterprise_installation/download-package.md
index 6cc7a602ff..e051e1cc9e 100644
--- a/data/reusables/enterprise_installation/download-package.md
+++ b/data/reusables/enterprise_installation/download-package.md
@@ -1,4 +1,4 @@
1. Download the upgrade package to {% data variables.product.product_location %} using `curl `:
```shell
-admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL
+admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL
```
diff --git a/data/reusables/enterprise_installation/generate-replication-key-pair.md b/data/reusables/enterprise_installation/generate-replication-key-pair.md
index 7f7056e59a..66c04ee3ed 100644
--- a/data/reusables/enterprise_installation/generate-replication-key-pair.md
+++ b/data/reusables/enterprise_installation/generate-replication-key-pair.md
@@ -1,4 +1,4 @@
7. To generate a key pair for replication, use the `ghe-repl-setup` command with the primary appliance's IP address and copy the public key that it returns.
```shell
- $ ghe-repl-setup PRIMARY IP
+ $ ghe-repl-setup PRIMARY_IP
```
diff --git a/data/reusables/enterprise_installation/replica-ssh.md b/data/reusables/enterprise_installation/replica-ssh.md
index 3a28108630..b2c22e4905 100644
--- a/data/reusables/enterprise_installation/replica-ssh.md
+++ b/data/reusables/enterprise_installation/replica-ssh.md
@@ -1,4 +1,4 @@
1. Connect to the replica instance over SSH as the "admin" user on port 122:
```shell
-$ ssh -p 122 admin@replica-host
+$ ssh -p 122 admin@REPLICA_HOST
```
diff --git a/data/reusables/enterprise_installation/ssh-into-instance.md b/data/reusables/enterprise_installation/ssh-into-instance.md
index 01094fb67b..cd5b8ce2cd 100644
--- a/data/reusables/enterprise_installation/ssh-into-instance.md
+++ b/data/reusables/enterprise_installation/ssh-into-instance.md
@@ -1,5 +1,5 @@
1. SSH into {% data variables.product.product_location %}. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
```shell
- $ ssh -p 122 admin@HOSTNAME
+ $ ssh -p 122 admin@HOSTNAME
```
diff --git a/data/reusables/enterprise_installation/ssh-into-target-instance.md b/data/reusables/enterprise_installation/ssh-into-target-instance.md
index 9c6a2495d5..a249949cdf 100644
--- a/data/reusables/enterprise_installation/ssh-into-target-instance.md
+++ b/data/reusables/enterprise_installation/ssh-into-target-instance.md
@@ -1,4 +1,4 @@
1. As a site admin, [SSH into your target {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
```shell
-$ ssh -p 122 admin@HOSTNAME
+$ ssh -p 122 admin@HOSTNAME
```
diff --git a/data/reusables/enterprise_migrations/unlocking-on-instances.md b/data/reusables/enterprise_migrations/unlocking-on-instances.md
index 67495e7227..29f0034a47 100644
--- a/data/reusables/enterprise_migrations/unlocking-on-instances.md
+++ b/data/reusables/enterprise_migrations/unlocking-on-instances.md
@@ -1,5 +1,5 @@
1. Unlock all the imported repositories with the `ghe-migrator unlock` command. You'll need your Migration GUID:
```shell
-$ ghe-migrator unlock -g MIGRATION_GUID
+$ ghe-migrator unlock -g MIGRATION-GUID
> Unlocked octo-org/octo-project
```
diff --git a/data/reusables/git/git-push.md b/data/reusables/git/git-push.md
index 2e99b1f21b..850aca63b9 100644
--- a/data/reusables/git/git-push.md
+++ b/data/reusables/git/git-push.md
@@ -1,5 +1,5 @@
1. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
```shell
- $ git push origin your-branch
+ $ git push origin YOUR_BRANCH
# Pushes the changes in your local repository up to the remote repository you specified as the origin
```
diff --git a/data/reusables/gpg/paste-gpg-key-id.md b/data/reusables/gpg/paste-gpg-key-id.md
index e0bb894d01..d75e15cb2e 100644
--- a/data/reusables/gpg/paste-gpg-key-id.md
+++ b/data/reusables/gpg/paste-gpg-key-id.md
@@ -1,9 +1,9 @@
1. To set your primary GPG signing key in Git, paste the text below, substituting in the GPG primary key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`:
```shell
- $ git config --global user.signingkey 3AA5C34371567BD2
+ $ git config --global user.signingkey 3AA5C34371567BD2
```
Alternatively, when setting a subkey include the `!` suffix. In this example, the GPG subkey ID is `4BB6D45482678BE3`:
```shell
- $ git config --global user.signingkey 4BB6D45482678BE3!
+ $ git config --global user.signingkey 4BB6D45482678BE3!
```
diff --git a/data/reusables/gpg/x-509-key.md b/data/reusables/gpg/x-509-key.md
index a303466a11..1f26fe3e15 100644
--- a/data/reusables/gpg/x-509-key.md
+++ b/data/reusables/gpg/x-509-key.md
@@ -15,7 +15,7 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
```
- To use S/MIME to sign for a single repository:
```shell
- $ cd /path/to/my/repository
+ $ cd PATH_TO_REPOSITORY
$ git config --local gpg.x509.program smimesign
$ git config --local gpg.format x509
```
@@ -26,7 +26,7 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
```
- To use S/MIME to sign for a single repository:
```shell
- $ cd /path/to/my/repository
+ $ cd PATH_TO_REPOSITORY
$ git config --local gpg.program smimesign
```
If you're using an X.509 key that matches your committer identity, you can begin signing commits and tags.
@@ -48,10 +48,10 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
6. To set your X.509 signing key in Git, paste the text below, substituting in the certificate ID you copied earlier.
- To use your X.509 key to sign for all repositories:
```shell
- $ git config --global user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f
+ $ git config --global user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f
```
- To use your X.509 key to sign for a single repository:
```shell
- $ cd /path/to/my/repository
- $ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f
+ $ cd PATH_TO_REPOSITORY
+ $ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f
```
diff --git a/data/reusables/package_registry/create-npmrc-owner-step.md b/data/reusables/package_registry/create-npmrc-owner-step.md
index af4ee63bcd..2d49a24d9c 100644
--- a/data/reusables/package_registry/create-npmrc-owner-step.md
+++ b/data/reusables/package_registry/create-npmrc-owner-step.md
@@ -2,15 +2,15 @@
{% ifversion fpt or ghec %}
```shell
- @OWNER:registry=https://npm.pkg.github.com
+ @OWNER:registry=https://npm.pkg.github.com
```
{% else %}
If subdomain isolation is enabled:
```shell
- @OWNER:registry=https://npm.HOSTNAME
+ @OWNER:registry=https://npm.HOSTNAME
```
If subdomain isolation is disabled:
```shell
- @OWNER:registry=https://HOSTNAME/_registry/npm
+ @OWNER:registry=https://HOSTNAME/_registry/npm
```
{% endif %}
diff --git a/data/reusables/pages/remove-submodule.md b/data/reusables/pages/remove-submodule.md
index 4e1201dcd4..63c2baba8b 100644
--- a/data/reusables/pages/remove-submodule.md
+++ b/data/reusables/pages/remove-submodule.md
@@ -1,9 +1,9 @@
To troubleshoot, first decide if you actually want to use a submodule, which is a Git project inside a Git project; submodules are sometimes created accidentally.
-If you don't want to use a submodule, remove the submodule, replacing PATH-TO-SUBMODULE with the path to the submodule:
+If you don't want to use a submodule, remove the submodule, replacing PATH-TO-SUBMODULE with the path to the submodule:
```shell
-$ git submodule deinit PATH-TO-SUBMODULE
-$ git rm PATH-TO-SUBMODULE
+$ git submodule deinit PATH-TO-SUBMODULE
+$ git rm PATH-TO-SUBMODULE
$ git commit -m "Remove submodule"
-$ rm -rf .git/modules/PATH-TO-SUBMODULE
+$ rm -rf .git/modules/PATH-TO-SUBMODULE
```
From d14b2413deecdfb866eb585da36d6658f7d5dd40 Mon Sep 17 00:00:00 2001
From: Dev Prakash Sharma
Date: Mon, 3 Oct 2022 00:46:57 +0530
Subject: [PATCH 04/15] updated code-examples
---
.../upgrading-github-enterprise-server.md | 4 ++--
.../preparing-to-migrate-data-to-your-enterprise.md | 10 +++++-----
.../webhooks-and-events/webhooks/creating-webhooks.md | 2 +-
data/reusables/gpg/x-509-key.md | 6 +++---
4 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index 4770717072..25334f84d1 100644
--- a/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -176,8 +176,8 @@ While you can use a hotpatch to upgrade to the latest patch release within a fea
6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
```shell
*** applying update...
- This package will upgrade your installation to version version-number
- Current root partition: /dev/xvda1 [version-number]
+ This package will upgrade your installation to version VERSION-NUMBER
+ Current root partition: /dev/xvda1 [VERSION-NUMBER]
Target root partition: /dev/xvda2
Proceed with installation? [y/N]
```
diff --git a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
index f2f285ece1..2e743d65b5 100644
--- a/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
+++ b/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -30,7 +30,7 @@ shortTitle: Prepare to migrate data
3. Use the `ghe-migrator prepare` command to prepare the archive for import on the target instance and generate a new Migration GUID for you to use in subsequent steps:
```shell
- ghe-migrator prepare /home/admin/MIGRATION_GUID.tar.gz
+ ghe-migrator prepare /home/admin/MIGRATION-GUID.tar.gz
```
* To start a new import attempt, run `ghe-migrator prepare` again and get a new Migration GUID.
@@ -40,7 +40,7 @@ shortTitle: Prepare to migrate data
1. Using the `ghe-migrator conflicts` command with the Migration GUID, generate a *conflicts.csv* file:
```shell
- $ ghe-migrator conflicts -g MIGRATION_GUID > conflicts.csv
+ $ ghe-migrator conflicts -g MIGRATION-GUID > conflicts.csv
```
- If no conflicts are reported, you can safely import the data by following the steps in "[Migrating data to your enterprise](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/)".
2. If there are conflicts, using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command, copy *conflicts.csv* to your local computer:
@@ -118,7 +118,7 @@ Given a list of usernames from the source and a list of usernames on the target,
You can quickly generate a CSV of users being migrated in the CSV format needed to apply custom mappings by using the [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) command:
```shell
-$ ghe-migrator audit -m user -g MIGRATION_GUID > users.csv
+$ ghe-migrator audit -m user -g MIGRATION-GUID > users.csv
```
Now, you can edit that CSV and enter the new URL for each user you would like to map or rename, and then update the fourth column to have `map` or `rename` as appropriate.
@@ -142,7 +142,7 @@ The same process can be used to create mappings for each record that supports cu
2. Re-map the migration data using the `ghe-migrator map` command, passing in the path to your modified *.csv* file and the Migration GUID:
```shell
- $ ghe-migrator map -i conflicts.csv -g MIGRATION_GUID
+ $ ghe-migrator map -i conflicts.csv -g MIGRATION-GUID
```
-3. If the `ghe-migrator map -i conflicts.csv -g MIGRATION_GUID` command reports that conflicts still exist, run through the migration conflict resolution process again.
+3. If the `ghe-migrator map -i conflicts.csv -g MIGRATION-GUID` command reports that conflicts still exist, run through the migration conflict resolution process again.
diff --git a/content/developers/webhooks-and-events/webhooks/creating-webhooks.md b/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
index 4a2fc2da67..4891b1b676 100644
--- a/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
+++ b/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
@@ -26,7 +26,7 @@ For the purposes of this tutorial, we're going to use a local server to receive
After installing `ngrok`, you can expose your localhost by running `./ngrok http 4567` on the command line. 4567 is the port number on which our server will listen for messages. You should see a line that looks something like this:
```shell
-$ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
+$ Forwarding http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
```
Make a note of the `*.ngrok.io` URL. We'll use it to set up our webhook.
diff --git a/data/reusables/gpg/x-509-key.md b/data/reusables/gpg/x-509-key.md
index 1f26fe3e15..26e14aa402 100644
--- a/data/reusables/gpg/x-509-key.md
+++ b/data/reusables/gpg/x-509-key.md
@@ -15,7 +15,7 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
```
- To use S/MIME to sign for a single repository:
```shell
- $ cd PATH_TO_REPOSITORY
+ $ cd PATH-TO-REPOSITORY
$ git config --local gpg.x509.program smimesign
$ git config --local gpg.format x509
```
@@ -26,7 +26,7 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
```
- To use S/MIME to sign for a single repository:
```shell
- $ cd PATH_TO_REPOSITORY
+ $ cd PATH-TO-REPOSITORY
$ git config --local gpg.program smimesign
```
If you're using an X.509 key that matches your committer identity, you can begin signing commits and tags.
@@ -52,6 +52,6 @@ You can use [smimesign](https://github.com/github/smimesign) to sign commits and
```
- To use your X.509 key to sign for a single repository:
```shell
- $ cd PATH_TO_REPOSITORY
+ $ cd PATH-TO-REPOSITORY
$ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f
```
From 92e153eaf55428935157b2288af7cd2516bc78e0 Mon Sep 17 00:00:00 2001
From: Dev Prakash Sharma
Date: Mon, 3 Oct 2022 00:49:17 +0530
Subject: [PATCH 05/15] Merge branch 'codewithdev-changes' of
https://github.com/codewithdev/docs into codewithdev-changes
From 69ce3069c1a2293fc690d81460dbb826581afb74 Mon Sep 17 00:00:00 2001
From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Date: Mon, 3 Oct 2022 11:11:29 -0700
Subject: [PATCH 06/15] Apply suggestions from code review
---
.../setting-your-commit-email-address.md | 2 +-
...-on-macos-runners-for-xcode-development.md | 2 +-
.../autoscaling-with-self-hosted-runners.md | 2 +-
...and-troubleshooting-self-hosted-runners.md | 4 ++--
.../command-line-utilities.md | 2 +-
.../configuring-a-repository-cache.md | 4 ++--
...-availability-replication-for-a-cluster.md | 20 +++++++++----------
...ng-github-desktop-from-the-command-line.md | 6 +++---
.../overview/using-ssh-agent-forwarding.md | 4 ++--
...a-git-repository-using-the-command-line.md | 2 +-
.../guides/forming-calls-with-graphql.md | 4 ++--
.../checking-out-pull-requests-locally.md | 2 +-
.../enterprise-admin/management-console.md | 4 ++--
13 files changed, 29 insertions(+), 29 deletions(-)
diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
index ced0c6c3fb..66e0967805 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
@@ -51,7 +51,7 @@ To ensure that commits are attributed to you and appear in your contributions gr
{% note %}
-**Note:** If you created your account on {% data variables.product.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of ID+username@users.noreply.github.com. If you created your account on {% data variables.product.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is username@users.noreply.github.com. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
+**Note:** If you created your account on {% data variables.product.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is a seven-digit ID number and your username in the form of ID+USERNAME@users.noreply.github.com. If you created your account on {% data variables.product.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is USERNAME@users.noreply.github.com. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
{% endnote %}
diff --git a/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md b/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
index be5b750a87..1459f98cd5 100644
--- a/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
+++ b/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md
@@ -63,7 +63,7 @@ Create secrets in your repository or organization for the following items:
- Use the following command to convert your provisioning profile to Base64 and copy it to your clipboard:
```shell
- base64 provisioning_profile.mobileprovision | pbcopy
+ base64 PROVISIONING_PROFILE.mobileprovision | pbcopy
```
* A keychain password.
diff --git a/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 7d67ea775c..e2894b8fdd 100644
--- a/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -63,7 +63,7 @@ By default, self-hosted runners will automatically perform a software update whe
To turn off automatic software updates and install software updates yourself, specify the `--disableupdate` flag when registering your runner using `config.sh`. For example:
```shell
-./config.sh --url https://github.com/octo-org --token EXAMPLE-TOKEN --disableupdate
+./config.sh --url https://github.com/YOUR-ORGANIZATION --token EXAMPLE-TOKEN --disableupdate
```
If you disable automatic updates, you must still update your runner version regularly. New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software. The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
diff --git a/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
index c828388039..02a70e8c26 100644
--- a/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
+++ b/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -59,7 +59,7 @@ For example:
{% windows %}
```shell
-run.cmd --check --url https://github.com/octo-org/octo-repo --pat gcp_abcd1234
+run.cmd --check --url https://github.com/YOUR-ORG/YOUR-REPO --pat GHP_ABCD1234
```
{% endwindows %}
@@ -79,7 +79,7 @@ To disable TLS certification verification in the self-hosted runner application,
```shell
export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1
-./config.sh --url https://github.com/octo-org/octo-repo --token
+./config.sh --url https://github.com/YOUR-ORG/YOUR-REPO --token
./run.sh
```
diff --git a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index 1fcaf9bf0e..6ce475f511 100644
--- a/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -115,7 +115,7 @@ With this utility, you can both retrieve and modify the configuration settings o
$ ghe-config core.github-hostname
# Gets the configuration value of `core.github-hostname`
$ ghe-config core.github-hostname URL
-# Sets the configuration value of `core.github-hostname` to URL for example, `example.com`
+# Sets the configuration value of `core.github-hostname` to the specified URL
$ ghe-config -l
# Lists all the configuration values
```
diff --git a/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
index bc6312c9e2..708967668a 100644
--- a/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
+++ b/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
@@ -45,7 +45,7 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins
1. Connect to the repository cache's IP address using SSH.
```shell
- $ ssh -p 122 admin@REPLICA IP
+ $ ssh -p 122 admin@REPLICA-IP
```
{%- ifversion ghes = 3.3 %}
1. On your cache replica, enable the feature flag for repository caching.
@@ -59,7 +59,7 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins
1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again.
```shell
- $ ghe-repl-setup PRIMARY IP
+ $ ghe-repl-setup PRIMARY-IP
```
1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter.
diff --git a/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md b/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
index 51b1594478..1291e253e1 100644
--- a/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
+++ b/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
@@ -80,7 +80,7 @@ Before you define a secondary datacenter for your passive nodes, ensure that you
[cluster "HOSTNAME"]
datacenter = default
hostname = HOSTNAME
- ipv4 = IP ADDRESS
+ ipv4 = IP-ADDRESS
...
...
```
@@ -185,8 +185,8 @@ For an example configuration, see "[Example configuration](#example-configuratio
11. Designate the primary MySQL and Redis nodes in the secondary datacenter. Replace `REPLICA MYSQL PRIMARY HOSTNAME` and `REPLICA REDIS PRIMARY HOSTNAME` with the hostnames of the passives node that you provisioned to match your existing MySQL and Redis primaries.
```shell
- git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA MYSQL PRIMARY HOSTNAME
- git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA REDIS PRIMARY HOSTNAME
+ git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA-MYSQL-PRIMARY-HOSTNAME
+ git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA-REDIS-PRIMARY-HOSTNAME
```
{% warning %}
@@ -235,11 +235,11 @@ The top-level `[cluster]` configuration should look like the following example.
```shell
[cluster]
- mysql-master = HOSTNAME OF ACTIVE MYSQL MASTER
- redis-master = HOSTNAME OF ACTIVE REDIS MASTER
- primary-datacenter = PRIMARY DATACENTER NAME
- mysql-master-replica = HOSTNAME OF PASSIVE MYSQL MASTER
- redis-master-replica = HOSTNAME OF PASSIVE REDIS MASTER
+ mysql-master = HOSTNAME-OF-ACTIVE-MYSQL-MASTER
+ redis-master = HOSTNAME-OF-ACTIVE-REDIS-MASTER
+ primary-datacenter = PRIMARY-DATACENTER-NAME
+ mysql-master-replica = HOSTNAME-OF-PASSIVE-MYSQL-MASTER
+ redis-master-replica = HOSTNAME-OF-PASSIVE-REDIS-MASTER
mysql-auto-failover = false
...
```
@@ -250,8 +250,8 @@ The configuration for an active node in your cluster's storage tier should look
...
[cluster "UNIQUE ACTIVE NODE HOSTNAME"]
datacenter = default
- hostname = UNIQUE ACTIVE NODE HOSTNAME
- ipv4 = IPV4 ADDRESS
+ hostname = UNIQUE-ACTIVE-NODE-HOSTNAME
+ ipv4 = IPV4-ADDRESS
consul-datacenter = default
consul-server = true
git-server = true
diff --git a/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md b/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
index b0f93f2234..bdcff0058c 100644
--- a/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
+++ b/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
@@ -22,7 +22,7 @@ versions:
You can also change to your repository path and then type `github .` to open that repository.
```shell
- $ cd /path/to/repo
+ $ cd /PATH/TO/REPO
[repo]$ github .
```
@@ -34,13 +34,13 @@ versions:
2. {% data reusables.desktop.launch-desktop-from-command-line %}
```shell
- C:\Users\octocat> github path\to\repo
+ C:\Users\octocat> github PATH\TO\REPO
```
You can also change to your repository path and then type `github .` to open that repository.
```shell
- C:\Users\octocat> cd repo\myrepo
+ C:\Users\octocat> cd REPO\MY-REPO
C:\Users\octocat\repo\myrepo> github .
```
diff --git a/content/developers/overview/using-ssh-agent-forwarding.md b/content/developers/overview/using-ssh-agent-forwarding.md
index a0f3e4dfa2..7921be217c 100644
--- a/content/developers/overview/using-ssh-agent-forwarding.md
+++ b/content/developers/overview/using-ssh-agent-forwarding.md
@@ -97,8 +97,8 @@ Before you can make your keys work through agent forwarding, they must work loca
Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal:
```shell
-$ ssh -v "example.com"
-# Connect to example.com with verbose debug output
+$ ssh -v URL
+# Connect to the specified URL with verbose debug output
> OpenSSH_8.1p1, LibreSSL 2.7.3
> debug1: Reading configuration data /Users/YOU/.ssh/config
> debug1: Applying options for example.com
diff --git a/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
index 15aceafdb9..e570aed9dc 100644
--- a/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
+++ b/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
@@ -37,7 +37,7 @@ For purposes of demonstration, we'll use:
3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
```shell
$ cd REPO.git
- $ git push --mirror https://{% data variables.command_line.codeblock %}/ghuser/REPO.git
+ $ git push --mirror https://{% data variables.command_line.codeblock %}/USER/REPO.git
# Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}
```
4. Remove the temporary local repository.
diff --git a/content/graphql/guides/forming-calls-with-graphql.md b/content/graphql/guides/forming-calls-with-graphql.md
index e086d40fb2..eb64b6f601 100644
--- a/content/graphql/guides/forming-calls-with-graphql.md
+++ b/content/graphql/guides/forming-calls-with-graphql.md
@@ -106,8 +106,8 @@ To form a mutation, you must specify three things:
Mutations are structured like this:
mutation {
- mutationName(input: {MutationNameInput!}) {
- MutationNamePayload
+ MUTATION-NAME(input: {MUTATION-NAME-INPUT!}) {
+ MUTATION-NAME-PAYLOAD
}
}
diff --git a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
index a2f42020f0..0740282958 100644
--- a/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
+++ b/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -74,7 +74,7 @@ Anyone can work with a previously opened pull request to continue working on it,
7. At this point, you can do anything you want with this branch. You can run some local tests, or merge other branches into the branch.
8. When you're ready, you can push the new branch up:
```shell
- [pull-inactive-pull-request] $ git push origin BRANCHNAME
+ [pull-inactive-pull-request] $ git push origin BRANCH_NAME
> Counting objects: 32, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (26/26), done.
diff --git a/content/rest/enterprise-admin/management-console.md b/content/rest/enterprise-admin/management-console.md
index 0f1095eb85..961fc9d74a 100644
--- a/content/rest/enterprise-admin/management-console.md
+++ b/content/rest/enterprise-admin/management-console.md
@@ -25,11 +25,11 @@ You need to pass your [Management Console password](/enterprise/admin/articles/a
Use the `api_key` parameter to send this token with each request. For example:
```shell
-$ curl -L 'https://HOSTNAME:ADMIN-PORT/setup/api?api_key=YOUR_AMAZING_PASSWORD'
+$ curl -L 'https://HOSTNAME:ADMIN-PORT/setup/api?api_key=YOUR_PASSWORD'
```
You can also use standard HTTP authentication to send this token. For example:
```shell
-$ curl -L -u "api_key:YOUR_AMAZING_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api'
+$ curl -L -u "api_key:YOUR_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api'
```
From af13d81f7555d2ad115311ed5e65dc173878619b Mon Sep 17 00:00:00 2001
From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Date: Mon, 3 Oct 2022 11:13:16 -0700
Subject: [PATCH 07/15] Apply suggestions from code review
---
.../managing-commit-signature-verification/signing-commits.md | 2 +-
.../overview/launching-github-desktop-from-the-command-line.md | 2 +-
.../creating-and-managing-repositories/cloning-a-repository.md | 3 +--
data/reusables/actions/self-hosted-runner-check-mac-linux.md | 3 +--
4 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/content/authentication/managing-commit-signature-verification/signing-commits.md b/content/authentication/managing-commit-signature-verification/signing-commits.md
index faeeb878b6..e9b3200e36 100644
--- a/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -36,7 +36,7 @@ If you have multiple keys or are attempting to sign commits or tags with a key t
1. When committing changes in your local branch, add the -S flag to the git commit command:
```shell
- $ git commit -S -m YOUR_COMMIT_MESSAGE
+ $ git commit -S -m "YOUR_COMMIT_MESSAGE"
# Creates a signed commit
```
2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
diff --git a/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md b/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
index bdcff0058c..edcbbd0900 100644
--- a/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
+++ b/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
@@ -16,7 +16,7 @@ versions:
3. {% data reusables.desktop.launch-desktop-from-command-line %}
```shell
- $ github /path/to/repo
+ $ github /PATH/TO/REPO
```
You can also change to your repository path and then type `github .` to open that repository.
diff --git a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
index c8bf281fc9..d5ff6f38b6 100644
--- a/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -48,9 +48,8 @@ gh repo clone REPOSITORY
You can also use the GitHub URL to clone a repository.
```shell
-gh repo clone URL
+gh repo clone https://github.com/PATH-TO/REPOSITORY
```
-Replace URL with the URL of a GitHub repository. For example, `https://github.com/cli/cli`
{% endcli %}
diff --git a/data/reusables/actions/self-hosted-runner-check-mac-linux.md b/data/reusables/actions/self-hosted-runner-check-mac-linux.md
index 5a946bfa75..ca32cd3f4a 100644
--- a/data/reusables/actions/self-hosted-runner-check-mac-linux.md
+++ b/data/reusables/actions/self-hosted-runner-check-mac-linux.md
@@ -1,4 +1,3 @@
```shell
./run.sh --check --url URL --pat ghp_abcd1234
-```
-Replace URL with the URL of repository. For example, `https://github.com/octo-org/octo-repo`.
\ No newline at end of file
+```
\ No newline at end of file
From d5ba742c2f1efa317c441fb727d6dec7dc82d338 Mon Sep 17 00:00:00 2001
From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Date: Mon, 3 Oct 2022 13:16:57 -0700
Subject: [PATCH 08/15] fix liquid tag
---
.../working-with-the-gradle-registry.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
index dc5f62a139..2646465644 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -192,7 +192,7 @@ To use a published package from {% data variables.product.prodname_registry %},
```shell
repositories {
maven {
- url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else % REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+ url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
credentials {
username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
From 39cd30a2abb03609b0dbf493ea09432f1dd3d4c8 Mon Sep 17 00:00:00 2001
From: Jim Boyle <95828167+boylejj@users.noreply.github.com>
Date: Tue, 4 Oct 2022 10:48:14 -0400
Subject: [PATCH 09/15] Update streaming-the-audit-log-for-your-enterprise.md
for OIDC GA (#31164)
---
.../streaming-the-audit-log-for-your-enterprise.md | 6 ------
1 file changed, 6 deletions(-)
diff --git a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
index b34b1c60c3..47804fb2d7 100644
--- a/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
+++ b/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -86,12 +86,6 @@ For information on creating or accessing your access key ID and secret key, see
{% ifversion streaming-oidc-s3 %}
#### Setting up streaming to S3 with OpenID Connect
-{% note %}
-
-**Note:** Streaming to Amazon S3 with OpenID Connect is currently in beta and subject to change.
-
-{% endnote %}
-
1. In AWS, add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
- For the provider URL, use `https://oidc-configuration.audit-log.githubusercontent.com`.
From b8f3aa6aa64dbd15a6f50b3500ec32a5df55036f Mon Sep 17 00:00:00 2001
From: Sam Browning <106113886+sabrowning1@users.noreply.github.com>
Date: Tue, 4 Oct 2022 10:56:28 -0400
Subject: [PATCH 10/15] Add period in "Configuring code scanning" section
(#31385)
---
.../code-security/getting-started/securing-your-organization.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md
index e560122037..b86ed3fe6a 100644
--- a/content/code-security/getting-started/securing-your-organization.md
+++ b/content/code-security/getting-started/securing-your-organization.md
@@ -116,7 +116,7 @@ For more information, see "[Managing security and analysis settings for your org
## Configuring {% data variables.product.prodname_code_scanning %}
-{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors
+{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors.
{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
From 5399c5b0096b32354a466a76abd96be831d41ce2 Mon Sep 17 00:00:00 2001
From: Sam Browning <106113886+sabrowning1@users.noreply.github.com>
Date: Tue, 4 Oct 2022 11:49:35 -0400
Subject: [PATCH 11/15] Sunset Atom in the Docs (#31315)
Co-authored-by: github-actions
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
---
.../images/help/desktop/mac-editor-menu.png | Bin 70634 -> 60308 bytes
.../help/desktop/windows-editor-menu.png | Bin 27649 -> 15245 bytes
...-guidelines-for-repository-contributors.md | 2 +-
.../making-changes-in-a-branch/index.md | 2 +-
.../configuring-a-default-editor.md | 2 --
.../github-extensions-and-integrations.md | 6 +---
.../associating-text-editors-with-git.md | 27 ------------------
...etting-started-with-your-github-account.md | 2 +-
.../git-and-github-learning-resources.md | 2 +-
.../basic-writing-and-formatting-syntax.md | 2 +-
...-and-searching-issues-and-pull-requests.md | 2 +-
...a-merge-conflict-using-the-command-line.md | 4 +--
.../searching-issues-and-pull-requests.md | 2 +-
.../about-github-premium-support.md | 2 +-
14 files changed, 11 insertions(+), 44 deletions(-)
diff --git a/assets/images/help/desktop/mac-editor-menu.png b/assets/images/help/desktop/mac-editor-menu.png
index 78162a29363fba8dea933f7a497e0e94d90e3683..df7c1878e6cc8580077a61e284ca3664684601ff 100644
GIT binary patch
literal 60308
zcmeFYcT`hb*FK5}0tzBX5ot=1-bIiWKspGaHv#FLNbiIqA|N1LM2ghVn}F0PMLI|g
z9cj`DJ+vfu<2mO&@A&Q*_wW1rjc<)4yRNk}Ag_fTaTYd!q(
zGynBG9vR2Ayw^W*m5@2)2{@lS?h$gHRKtEvcj7+r(3ShHQj`5QL%s^t85&j1OSRpb
zPVv*z>})<@VfG9Ovc>~e`X+1D!)xzWl5}ot5M>9O2NS;w
z#!uCMU?Z=nh+}YL2A=ATxW?pIA=>)|Gleyaeq;vzb{!}3jcAzJx4wwe2RJ^g8r&Rs
z!R*UCkEo-p@9Aapgj|zt2EVDH_^S0rh{C60_K{Qyi7PFRl`gM-0)Fr`YqwC8k0JP3
z8L5RWnHf8-bjGzRNDxL&s$=8Mj4Z7{hhU)14^lBh=xG1FkrlU^HYF!1my({O
zv);8#ZvA<#MwFhvGUUeU1{X9#X5jkRd!K`J+QV9ObiT{Q$R8=D|xGj#8SJOx@So
zV&~tO`V_7c-FWffnxQlfU2^}gw=BMKgr>{V0;hMGuCd>{PyGN%8O+oTrMIBeSA5Tb
zTbY68eSMJ$7`FG21LhNG3EiTd@=>#RE*oDKeZSObuX@soI^he!b
z#xE>4$gW3z?s%C)@ACFyY2F8~`MiBIRLFJcyKg`}o5Vv8at88pvPQ!CM}%uCK~ZkR
z>!Ii0dtX>xez-Mz-=T5w+E-GYh~BTfE`)Th`s)$l7cxUG@2$C(Q>?@H6HgXw_S#3m
z)0&?+*yZDvG^)_Pc^_Lo&b*J}Mu2`Rk~#hWw@y8i1YOu--v>%LwL|MVs4NI7g(iu%
z>Adh9afnOt9XqD0as?&6G&1z*BeLrad?gydil?N|Fb%zw9^AG2YYc0AQLVDyDW=5l
zSF%MFs=PLw3MZzzWFovrM>b?H+TJT@ydiNiaiTxRg2UfK3x9}l{Z;p(!{!)NQ{
z9y~_jy9!&wch~Wc?oWreN?!;B7rku!K=b>pfWQ-~@O+E34|wU3$rh^ylzP#^?P~$}
zTWx+-aiU~}%fz!}<-foZ*VYyj_tH)+0wi1SR&>qmah+aoCdDdblf5InjmL)@@m{T)
zN$pY6onE3Dq6osmU#6RnnwiNX8|7$o2xg->I_Q=jFIg`Taz^SE7+ps`6YOsTE~4$5c3-nmTKAw|md(iph%QO5aN1$`A!f6lG^L
zx%{GbfmVuEo#salYL2<2A)V*NB;yhHH3mKpelE|S(9+OEYAwKEun#3Z#T_t0U7M0p
z-Ki2cz15IjMO_|Uf89EVkHtEkk(;;2my7Fl7Jk}2cKit9N!C*`mMtmB$eSw+1m~7K
zEpi<@b*LHR9NQe{Eospygc%prjCGYzm!y_3g5j|F5}D!3iI>k_C{#-}o
zImV8?8|g>9C~Z(Z{PbIhCn2R)?>&{7W9x)oS)x(g`n|c(!Ggo}!}XcIly-`pDs!
zcdG@#Sb(hH`^h(6F$yoh_5_>Xv3l=VIh+0cSLQ<(JIFmt(WzItiyZCq=F{!X5&LhF
zZ_j|X>&P6eAQX;|2kc5Tn>687k*;s6CVevYm6uKLn%spZ(k1FX>QeJl+bC!)kR8=6
z;3*iQ5hJEzj;l%;{;@73BzQ|W@uRcA7XO8li)H3ZDMa(&WhVZ3sC~SBRd3FC&d|u1
z+q+edzWaSMdK6p*x^?6CON8{0WzMCErPKx@2B4bZ`o&3#nX$>)+We{WDfQ~I>J|sZ
zFP77*)6SJmR&mo!Q?@hulV%>$^t1G@Z`0C=McjSkf18@5;(k!O=6L+7!HU81={IEr
zN1J`QcGzeiSqih3A~&O}O^1lB$eP5O^PsnaLkuzPQ*W!oZUpZMuSDw2)RJ7g+)%}V
z`{SaU$t7VW-#l}-o{Kcj+^ffTDRVKKlbmJUt=*MmNMYDuNM;cEFx_wW+v2yOMyPG@
z8ut)$CS%KN%gvS(fAs3kdd5~u-^G+&`f%v*i~{ID0JV7Tw7+p+eOhqga_ZEsi%FZAm|Lv>YrpPsT7+GM4&rJL>ML
zT*^&SgEq5Cu4_MNV~1#=9--%WyRWZrygtf1GTAWusyWN)0=>bOE0`PC^}B4b<=4fb
z{=Pq+R48R=VVYDLmtdClnN?Z;X3t3<@6aw~b@*0zg`2GVlhx*-nBKW~@%O1o`l%X&
z8bc6r`$#u==ey4zsi#eHc-={T+w{oyxsha%208DPX)wh*E<5hAH=u(ZE#nQo5d!&E
zc}jW4M{Md+{PONmb}AP-7e&zpQarbLG0yj;VnoV38>fz*jxzSY9GDcmo0cX}oMbT!pMl$N?1#q}j@rBeF4My>WFo-rQJ5z}vLW45>vJjN*Nz>{-F%4?LK$qLEQ
zoC}a&kgv_dP|KZ1%g?RTrJSi;S{qocR0ESebR4UG4`~nUH+SC5^wmM<
z9!?L}3VGQY*D87*^X8hUI{v(G|9oio%UtRS-mZPAXX%_)p|O4)^>*@ZU@KqX!ZCXB
z!kCnwbd2GPn1S!xAlMg%qAa5Y#QV9Q;~z#Qrzj@Irnlz;)+q)PA!d&lldcugS>BDq5J)y-C4w7lXuFj_l)
zy(I$4n_F+}fuC*b&6nxdN4r2q$lemRIl|*pzj_Z7CwEE
zaM5U{Y)aB>dimqmKx}9oSx#_rUk6&R^T>32$%+fFp9?>ywT9&)s;i?CbyRUnd5x
z;mBw|Q&tAH+LmtC)-LXL5RY@=-b&yE(JLiGcN`ol)~oL|Wi6IH;Q0u99Rm-8=W1e>
z5NBRa&iA#EI>fMt1Em0y!?Fsc{Wg0;_9pz*xtw5$xzPT8PFNfhLngX
zzr>&W|6f=BZSlWq8vI*RK;Wt1e^>plOaHT~uDi9{Gl(;of9d(pSwPWJHzoM~(`iyS?|#Ew0Q!;6UQR;?*aB8|Rj$1Oe%Sxo0{hnp<%uLq
z4RCN~jg{qObbO|_TOv~F5S|q!*yXb0iQ|?e=bnUB{~d3hscN3S1gGAF=aD)E9o+nD
zYEe(4p5A;w82mt*KNL?n7*C0bEQAm*UWh;Jllv!}U(ILZFA>{fCUc{A#eZE)Oqcj`
z?i6okN)-m#A_H5$1dZ0c+WWcq=bf&8er72pCOkQ2?cn(56pUh|ptZyKpTl64Q0c32
z^rukbhg^aAKZWxqF6BS_Iuv+UqwY_Eu@hd&{ilF6?*M@Ruacef0DLvDu8Oq03^17f
zD#20z+rZzd`2SMTxW@KelSrvi%Oj`hFHh;jz24FOqrq1R#niA^2Fd%k8KvmFwr6Qh
zwx?)g>7FK3O-xJ_OL}J@#}RY)TF-Wnulb;>724@f0v|0%{G{dwc%+FNQ@~A@w@!j@N_lr(Q5cO{38s_KE
zpWPy)e?Rg($@T7|H+>aNlD<1bflbfmh;*u{P3esG4}*R!DhjSWUd+`v9r~yJpl7&=
zhWf7`-7V}t5Bqo*_QYj2X?n!Eul+0Oj|ic`OZo3!hpivXh7ViUm-+3XnoZcT7Mg-*ZD;TyDFA
zvZ&t>(=#Z<`tdv#7N(~2$A(;2J{tXL-rlY~BtdN&h#uf~JeghjARv}`_EuiVn0M4m
zfb*n$T1PC7Ei33r^U*=~UQb>RYdFsU;d-1S{;~*UihSM|h2C5Gnc8-Vf6EHAisy=>`j|oPzk?VQnhzX&em8_HhV9=?Fr+dzGCIY-a$`6+
z!Hu7}LbdZdI5eqolMPxevvkXMH*j1ep_-#BCvlH%V4NB!M
zFlfITsFKc4BVI-~OS29uE@|4fx-=e>E_OuTr7^3L_FU$v_x7Wcck3)QhPT4LQb2=L
z7T<03phxRwb5vh-5dR8WGhp0XTzFY
zWXYMgWodJ7@~%dNSw^5s$op#Z_8(SodU3DUCFKnds|;{zR;%g7y&uhVX_^Vrn+5T<
zZWo7oCO*;_c;U_s?u?fctB+vxm6*~iiUNr(mxlW1S;nI8&P
zt>~r~_VDh3u#k2AfqjLRkZvbPnkSV?o
znB5`n`2KQNqMuTgPY&)cg-q$yPU<1Y3V0f&3?P(ulR>ap!0D@=V}TNc)#$Yf_!k4-
zE%Q^+Vm09!3!SW9NbWjpzR}Dyc(kEIxNF-qZFNrdFO>xwv1#NL=ZUg9sANZJuMW1n
zly;G1mjCVZot+9s5vl#|Yu(6&C5TWpg_o;Rlyv}+L!LpT<9dH_$9q0;OR=Z#DXFavK>7Bz10oLASJJX$$#J@(GQ
zaMu)Rl~9O^e0S6G8ioM-fdSC*6X*E^|L5AEj0qkysS$1}Sdv~^#IAFuG-X!1&=AS?
zpSDuLNd`}a&M5Ex`l}fn2g;~CRIq_4_;qxBe6H!OEVWNMf}8nVxVqfj9JOlpK~+UR
zlKU|e#Gd)FckfbD=&xvIGNz4;ZMX1EnwCq~zFf=+rGUEyJkNL{DXE}=Uo7fZWI$46
zar6Uyz-?On*jrBl5_SI1C?-%L(j0%FH9o){l)oM&oj2a_0jl(~#mvIgl@*bfw#
zZZBCjCy&-cuzUc2kgSa{Pbwk$jOqHWZmykT(HXOC^ME
zbv3%f5y~t>P%s1uic|h}VGk+S<2}unkPhLooeQHx?8o&0u`$_~a;P)dUL}YT=)CMYJ@avYR$C
z{^|gnacS@H0)xCw(mSxIY~01UG}b|O#cXo&MJC8vJzBg442aH?rjRn_xsy$#snWd_GG(R%y!`w
z@sS)xAvsFV;&HmnZc#vI6ZC{DvXX=9`SFz#L(#w5ptL5^$#I=Ke+4*~wexuP!jCFZ
z!BM^|Rct~toH1oWx9P&*asj>s)wa}|-H_=oX=Va{i5(oYqB&UC&(r&!z_4u&HRp*z9_d=UsX_&8ay2;c}7)aCO)HtaNPS
zfzWVVuI!c$BUG?R`cp!N|M%dJjj>t)TCDMMz9;77^8xUSFP1;~#oqliV4k`tjs1&dS1iBlND}{1
zero#`q?yuYC@sA|FEt|N3b#xCI47Y^SnZlg;hNqktM7XK@L2>~%|x<_Jr^su=(Gtm
z1cY_elCdX=FCTB#inNUmNoD2D@EClBmA37Rt&z|^c_csOIS9S~STsP;-p%cKmwUO{
z%x1t1Qks;fDDmCK`d>kBd5r6A%5xhU8rB==qyj|u%f5WO0{Lg$pmQG!(O17-_8`MR
ztv7$)GPwX^v&1c5-wqhR^LhWP^`D>Bkr5|ZLa4($b~F$tt7&oRmzgH^eTt3Xx_BYcq^nVq`FO>mvKuiXifg7rldgR@Z%gc)6WwOFf6WLg*`v65ey}(BYjHjc2lnW^7r$J7bm_5+(;9NF|Px
zwEVdhLQ@uY=TKd5yypYq>&NVK{G>!i_47ftn%Ks!tbvaMaaZ)WG{~)&NGFhTKZ!bC
zH&Tf+M#`Arq5(v*L_1G1QD&Ak7FtwG(}okJ*@ruR73DGCS30EuhTOXk*;s@{2d*xM
zW?R7aWP_0VJA>>-fX7jZlB-@LXa&FGm8678rHK}4S1Fy8)C`gMpKK3om&ioBog{C(
zcsEZ4V-d>;96Ynmh`{?MdXtk1=F+@+q8?Y{+n3TWK#}2f9yiFoMF+4sF^qSB7Yz
z$N-2=5tu9@{);c@ut|+V3xM^ZDRJuuk2JeS?}n&sIPULz?uyKMIJ&SPBvFzdrpyrc
z&6?^OPTr*7+6}?ueMaV_Z{q&UO=HPUh$ppWe`03i1OO+{fTPGzcl0i4&^?!io!FHR
z`5k;fTNqQoWHfvd*f)Gv#}PtX$7dV&A9LjmGE4Dp1pP6eb`Cc18DXK(NqmGt_;PH+
zW`Q(9Iy=-aR}Y_aJmLUuOKwlhXOl#}e27;Jj2zbOnR-4$==Nk)-Y&Q~CWWRGk262c
zkTc7{s54$hOi{xdpVK70e7FLBxO*XJ|GN14YWSlTh=W4~_KV$cLVv5s+<8PlS}Ox4
z%Crrj|1@{LdL=)O5EcBLWq;VY3B&k)RK5L+dMT4EHn8OWSWViNuj{%hKJJGu#nla|
z&e|rO^gblWx3}=}?bZ7qT_@BL-ee}F^sS8$=3*(8ty|5}w2+jh;G%dzEV-V{>5v`~
zusz>WXoieqkV|eHHPkT#qI}7hyR)^?O2RM)2i@$0c;$2W7`AeMOlXL5te_WwsviB#
z7E3CTvGSx>tOazN0Ke-eQkDDY)F^n45~f4lSD~E*HVrHg6;uju+d=8Uhi!b}`6rxUK@
z>c*URw`++$E=iQfTZy^d^)74ARVM1K!Uy3RU4f$q1rdZGiwbqP!tZ52M$`V`>tn0>
zCh5C{ffPh9Nwox`lzv`cShq`>`}yv<5hG}Q9m1ne|DjVgg{uED|4WjOpP%GWCu!=r
zF%{ygrr2A)C#74%lEz={1mK*((&M)}>;qhj5efNyZlhQL4Ia@ZDVk;!S!^9)P2Wvs
zVV|#;OXn}p!qqLb7|69)UZm0U2~57a%(KgXtTMMHTFb+GXPy=}IVklI@5={Yv;HBc
z!m(ou++=EUNvSy#n;LZF*V}1Q8u<*H_k~p-TnYRDtQ#YptgqC`fpQ$&l9rTJnq$m38Ro*6bk;uu-v(#*()D
z(pKaD2u!CrQZ3SDD8PV;);fK-K6>sA3?q*WvJ-xqa-%D`*vBSRP}n@qvs
zK1Y#-BV(lP3MGLo(p3bvB}LaEks38?{R3~6G1sIm#v7=Kl@KiwIq1)txqJ6l>j@;}
z70w=$$GBZ=w5J08_jH7?@#aB+J!^dBxOPad7K5iVd2W)P-9`5el3jMI3MC=F?Tu^l
z&_3?YXYo4p;b~bK4)t~!DaLZimuEUGIC#b7t`cnWC3Mlz32Q_;0H~Em|7eSeJgkz|
z@FDt$>+IDgSvw!Ig_x*CNs*g3T@woHU+
z7H!m{pS_dh-h7xh7M7vVw_`q5=ysGMUF(8A4@Gn5?~ibm^BU+E-xycri&KlEMYw7@
z7;Zd%E$p9g6BBUrX^CTuc^86
z7!awwCFrBJ=x0qVVCBbK#nSm=78&`TYi9>p@{n6P`{=~%dy0C>-~Nyhc$|2}f|WY0
z5(2*g22Vq=PZDtIo3M(plhzm8*HkN3nLZcRw6$doT`);z0i07|pFbyfLq>!&+U;#&
z2z5RlXQYd3#(hab4idRg27px@+G}f^if2}ga$y`g{mq;r#|_??R8c))&*$bXE=v*x
zrpQL@cM#R5XdCi(^@qZjja*=kaIw}KL=FPQe938%NUL6tPrNjWP)@&ojdO6UbpGSL
z@|!xQzv|a#4b~IaEAE?hGX3xayk(>3QXWT<@Z-l++q4K+Z}gWx6!4Wqgad6loW0*F
zw5<|9$2%Ga0bx-!daC;%Hx6WYBIWl!S{vUoK&1=}-FDVIiu6D}jqK{~9*sxpDjiXs(W$Sm;{tJV|~R0wn0LbJZ#P!=9*kuC|HkTM*MrWRWywbl`daW%k>>qSlfNdXpBiya(8m)w*k
z8E{f4ZLRcnq&=R&1^p~F*0A)H4-n739H71v$TS7Wl`MuW5#@8N_{D>2*wIW2TwPm$
zBb;=^O~wxJ3P;1zG`8v%nhZWv83n9TC@(;NNe??y78%D%vnnXo(0O^$??a%FywlFC
zu;&yxLz1y9(YCJt=@O<%SR=y|9b$9rq-x3<`x|
z6v^3das5vZ@Z->7xr)r^zDy}vcb$JUOK>L?k>e&Sh9+edRhHB^U3&lyXCY^&BIr$f
z^`QJ>1?z1YqSB_pp{a~3|H+H$mW~P}F=cBR@A}gfGUmJ{9a1fK^=!pRDl>nKJ&>N>3px@=@hMkI%yQ$m7edw?!d&pQy=q8
zC{uHOOcx<(lB`t9iyXa7sy1JWt1w#~wZB>+3*pP}oAi@Z>LATP&11per3gqFRG9OZ
zj_9HbM6o&1w@wlXZ7j6R2z7kJ-%?gRvDWO(+R|6vjre4`3FMUpvihCc^
zhLGO7_}8Ou>O}q2>98@)d&gvVpydIGxD+90KQKwd_zceRQJ62Tq@qc{_*U=p>N|y;
zv4dxUlu^GUbNd5SK5L;5ex7ZfFFlqUFfIJ3>hSFHV9NbB72UJ8jLn@+i`30v8V%4z
zVSi(@p-%YC+AVKMq?m{LM3BdcA@xOB%;*!#&)SFsAjDw}^M#N3T52G#z%zjk(Yyr)T64*b#+
zMiqJXX>XX#9`AMe!jOdC;5$uV-VM~ql(t^?)`t6^OIFb!54!Kd-dVCig>-Y3mr^Ra
z#!_LgnsXA5XlreDrg;b0i~TG82By_Kob)w~9}bs{1#%J8GLp{$D;im2%403N5D$7W
z0?-BbRaYN@2z5+m3ygr64=?SWj=CfaKm+f^6C~Wm99gyL9=Gvmat0X)eJ}Z7pEQ#j
zQD_m~sVZ-^Gucq{^7RaYv+6!)3kSFeCqRZIAyJ6FSlaIe7ppp@W-+6*aENp=A2?Z+
zQ^!1qb3B{QI@EIp=e@C7ur4rP!!RD-QIa%L~511MSW!5&d
z%`b`H7U$+GeKCNEE%%$TaH!yn-vAu&pZo~vT6X|DX-I-tm>+oB2$)Riw>seGJF*)U
zmDn?qXRriubgmlc^w&{*ba_#$+?bG(ld}W#P>;?EI$j~yKj+-gHIO%MP##g?ejTQF
zHAb!!h*O-Qt)3ml{OMdP`@V=d(*i#ZOti3Cdes(@bhTp9*Y(~G85b`y_1B8S(L273
zC~BTX*e9i8i4f(!-pEf0cW&T-Nj~-d^_DneH_Vo(aB#*%{?6V2?_5zaV^9D0@JieN
zCu`%F2@I@dbNfmLUHVwCsee*R-D=@EoT1s5svE?Xp?tRvW22#$%Z%95E)Zrv4tkk-
zKzh~d;4s`|;mwK3u8gp+-%%OY7l`&V-uXbcBu){hqW|3cry3M`PH>d~gjam?7p)^`
z+Nv+GeOLTekT~u4>K_Z<#0PbV3!e^R?D!V+B9?yk-^QT57m8Q35nizrd48#8oMLq8
zex0Y|L^(-`UIh_AsHi)2_UiU5_|>AS2aN0Ty6l{tdDf*p5OAd0Cbv`5G#U!f
zJE!UJ3%%3%4G`}Pwl(lVWgZG4Af?|NIgShRS96nspAH}eF%@4or}tJXEThLP8DmlC0Nvhe9$w~S`M(WJN^(ZWw;5JLB!81!sn+7Dy$~eVO
zK{NmCCd^?uobNL3;$?u_0?W^5badgQyb>`u60z9K@R)qN1|(tz>%J8M
z&B^CcyfLSYD;np1wLeBh<&Rpfzka{?!X@-8O;4aSTY|zCF
z5Y{qcjGSKgMp#{t2`ntGM?#xO#T3lW8G!^Nowr;FZ1l5f{9-t^3%YTc(m6J1QHM2sh>At-ugZvX;iyId(Xdy}h}E=bb2UCmXY
z{5mD;a$CPA2-$pLT8*}63*0zPU%;eVr5n4zg?6MrU`c;y5ZZn^i++!zJOr+Pzja;K(@m@!K3^=M(o)_k7rL|27*Ln?xWM;TH=$b^T9?zYw2I)>IcO7=
zJUGMa;FIbcws{M2VBM$x`WC^9k446w82QxK`Kqb;WIB()X;=Ulh%~UpNnmvRuo~E5
znx3bpNwUt&#w|9_e_&I1j1w+=Po7fe&1?!mSN7QwagqCk#jzC^6Z?iFj@VN5bN00h
z{q6H*^%BN-o;Az`lJU!~J&s2$4?gS8Y1ZUyDbCGintP-qadzaM<~;8YebK1S^g8x%dJ95T
zR>&gI7xzxNUuBaIZ5>2XFjcc=vw3~JrHmF>g-!!fo&XtlmSW^SogCG+`Du_V0}B!#
z8ZfmaF*M(Qe_3z-GE{BdCxmLsy)j-d)`C6pWhK*b?y4g!)e!Eb2K{rk$W=m`U+lszuj~f&fLS&ivFE@JPBeKp)XVLXT
z#h;L70qA`t2mMxTt7X)GCLRqFV3a}E@+q0X$2d20Ebr;+6
z@B{U(AkKau6kadg*V%XCpmK1om{0;;b}w(V_UV_ZO>m5KcVsmo10P7f85y`uC;HRW
zb|Wvi3bN2DM=S;`<80av&JJl;*?r5`e*=(K8Y4dnhEBOJQ5w+9($Rh4_D@+;ozW~&
zztVtc^>dZ0$z-Lgw%=UTBbAQ)C)yq3V;Y6581L;#8qDeX-J-ptLYXij1T?WDqt4R^
zwA;RK4!|zuyzz8MOQ2T&+19H$5)oT5kzyH7BXXJJ0ks(XrU*e=vM+%*;G&Nyn|m9u
zUZ0p1;~pWL5EUM+G0q4c|DBlnPj+LOOKWH@2emBn9@M20BMcTLP{D2+0)ZURF*A3z1OP!;B
zeH5x)m6OzZ4Moxd*^72|Tng`?q8v_nYkmU3VzPQlQZ&+~ghro=daS?tsNy}r7j!rF
ziEwy21pSOt&448V2~+C+=~p7NDt^DZX6PxOVFg877$8$yN(L5)-nAE(BMUQoUaZ-(
z;pbs5kwS?^3cjdkxXDD%9cl01yiD(Q2UgY!wpO4&e?43TQXlF}u9+8hDrN_N8Tos=~yE1sqSWGTf=dj4y7Q|MtYI*kyM2E8W$QJat7BNbuAbv7Q
zDy0_ALf?0xA7#-b?WrNNrjZpNTQsEB=lR08qFeOt(Y(*r&QarzZqbLjph;C`K?D-S
z6`6!Nj6+snFI%vu{tOpG7ngui{}ZRcTY=0!s4HGd*`a;7Uf~x5f#a`mdPsz{ytxN)
zJNpMyAza-TLY%z!(nRpf8HIaQ362&AP8>+eDwwTXrdL%c8`qgg!+qS0dh(;)pkS3DP#;DGHZBWg&<31*Y
zulWO+CdJ%}_}#jey5~0g;xsapaXDo#YB?oignjg
z&!7><_)?pGa&iaOUO+HJ#23aBL&@eLARR}eYHfCQHYAO
zsqP;lHUfX2)e~~=Bzj}5{XkGmTR$3p6jhRl_K@<;c-m6@ty$h?HByNj7Em~%2#&e;
zv^ZNRE$>F=5skOP090VHU#>q6l$InuvVn{@++Hw)3SfN~;9CC`0wGedTIdDQgCc|J
zm$Qs~6LCYdYO(e5*_*fv4K4ztaKK}?Y}6M|;BzvvuHJh5TVDI@j)mE$VUfz9l*DGu
zhm3AcF?EdLf+4GA!$^vEHfQm?3sZIu4l0-lFF%OI8z;o>T-qx~Mz=CTPQKaod(&n}
z5FJ+YQBOf5ylkDg9!RakMzgxXW?Tk
zwH-d6Y2ziE6vBhVT{5B3*;lSNM5cl_qc9*$w{K_q|+i7?5l79FD=uV5gZMBE669U8T8xiLZ|h
zM!r71G3PC-&~l=n0MleiAtIl6Sh>UMWsvk9`NeJyNXj0yY?k~z2V{1CV#(R6F|0{M
zeS8Y`tkmH*>5FYtkENF6Ug9``;3kjYJ5Md4O$*%{s8u78pAYQ=&#%mN!`>LWl2Yjndxp*^cTLHcIimW@)a7$Aw7
z9nc;|TTZCJG$_}az23?X}!lR2(CHie43>lRsha?|>_kV3{fS6i@z{v}Ck%*Uy>sdXkTe$P378a$3w!%c{*
z9Ki@O0xp1MT0yAGQ%?4I|GOm0LkK+?ql|TsC3ek}|G|_3ho2Gk1u&H4Y3ws%K>(?C
zGzlb*n*K7&$)tvDOBo-%FCR67n`m5F);Tbz4HaSC%CS9#S$%R>34j%YQfw_xkPA{Z
zGniNU=W~_r$GE!N*alF`d$|OTgkEpK7HFjJG&ZWFqVENKj&I=0dIjiYA$bTi1f54!
zjQtm2t6c+8uGoVUbGpO
zcM4U%W_s`HUlqKKrz0y!=;a#p7O+CiL3mvxM5WHUZ{ka?MbMDwR%(w}q%x-%gSUfJ
z+T*7Z2a|V|<6Xq#ZVxXzMpjzW=ZF%|0SmIHQ-OP!2olElC{d%Jyq$AXKVLb&)|q;U
zM(WmNqiJ++!qlfQqy3K1p@j=R)cH;eDhqYy?S=gpa2%iVO<<4Kth-L2{tNrkWk{^i<5Ugg;jpok
zY;Uw-knj9L)v1mPmNDe!RW=%4aS$17Y3Z%&u-pPHZJlBWv*^CDOryBe_P$kJXBK<`
zV>h-9{hp`+qD|p3V@RnmAk!;-L8DifhSA$U$nQ%D_uQJW6(b8%zsV`+oNM{yak*;h
z+)0GEPzK!&n`YZYiA{nW=Zr!H1b*n!h-svCxgDL#{rqI6#vAe|8JrX8=~Wt=63H;(
zI=tVEHOQ`BooKMH7(J@h$sQ39d!14dK7;%!?ljlPV_4|#dR!}FrA13AW8LLgA#+?S
zw-OmH<S~Z9%wAVbBC4Tlza(88sOZa>W3^do$PM9YHGf=}xPw
zmR&VF7ji)nJcX`4{>W1)DUbA5F3x9~-9B8XhnSu2)7a*B1)|VZ$~#qo&M4`PIL>$F
zj+&1RfB-vf3q_`L<$EV+YKKO=odRtUkTpm1jx4C{fBTYFC}ZtvXMt#2U$jx{U@}tw
z!mi{imVW3!zf@h<_FtPm*UgTyT{!Hd2yCYq8e3DeUb6RG{<$pbJVgB%6$6>?M%c?o
z1$CYDEnMcX%9+b*Zm
zxABo#NX)N@G)peQbs+Wox%Rx3AIM{JkKg^bZINg$jH&5|0J0@3vxdHJf^{SQDTV+@
zXxcu63o>bR9bXJtDWsc0V+F_24)6+ki+Cvlc@XPyEhfh#`vAiS-?WNaFhN=E!sofH
z_xIVdh_EPQY|^<|BNV%H?kt{fc@Fre
z8BY#3E@V(A5J;VMfZ{iWlv3>n+P2@ki7yFL
zg)!uxtm;}kB`&MJv=C|6#Zby31jT;<*=OV-s>s^GSV!4Z;O`5qOir_3ie4^cp4Y1<
z((?_$k@q$rl;LI#Zn|!!=$(a24=*(B6DMNTR31_wb$*i)TMgupg#+wp(ox0wRqiz<
zJm^16s2Lp7vQBx+W)rpP^GN4RM`jB<{h*wBGGHZn$5K{Xf^d7Q^?aS(EG2i+N~tbp
zq0nFl@HPy70$27W9O5wdhNt1|cV|J#abMYfHO+Z|PZi&`T}A6;9wW~|E~s@dQTS)j
zQD4f%9Vad=25-86F1bEZI??x+&J}=Dsz2>VeTyv
zm*@Q=(yl8>!WI)h4Vi8F%0i-Z3%CP^?t_iX6~>2NkWW(5VXk%{km*U
zkH3@qQME44CZQ%)$!R{qQ~FB*uJMeNuC1ZoVOn7_aj$Mqj@
zgtTI}@I|s1>;fG?4d54}<2NFlgD20AUCWBU=0%vfEa{nMOk>Iw!>_DYZ;eccypX$d
zDDG_sM^KPe=fqhzN7mXdbHUQ9mFBeP+-sn6Rx4(8)7RBxe2!nsEPsg;PBehKWPghj
zpU-%UUHZ2aUtg*}rl%3lL;`1$yy7oouOELBJqo9Fe*>S~D
zTUv$`$r=Rjw!WRyU@y6$brP|e2Wgc1?-r6jERu#4zs
zGNiQ)Jb7_Ku$nXN7C+o5=`}zYOQ?q7#w^7Fe8rPn`uy0Ueg)HolQ2C}gX?fo0c??W9fP_k*%wcI&<(dMl~w1xN2?YKaiULw6<$h
zmd0w0Gf&JA9%uAN!4Q?0f{C-V(*R2c*<{E&XS`n1Kmu80nR_~#JFlVI|D}q%
zpq{7o&ZVRdXcciiQ;^^;bo#`Uzh>3+i=d2Zm!NqsQ#E%&@1{j(&HqEzn}kLUB4Gu|_m#Dpk%EkPM>fpyDhnkT~*
zozDVA=8VKN@+tT4ZE`?C=CbMy=w`C%s9C^c@U_jsU?m37B(H^P)RLMx=n2ao?Q?m_Oj7w5B}A>+V#R*f@-8
zP@dFu)zCU=;LXYHpHoO%OM>bDIVnIc=+OgG;1&YbN{~n`M7t8m%oNgOk+K`&iL#fg
zIV*B?==e*CxNAH(Hx)UaV)2PyP3`tM@Qn7mm~4Eu3b&?#_A_HV+K>@fdo78rt;|Iz
zA-O_uac$}H;4d?^Ij3XgZ+Qd+-Qv-bu^xG{;6(7PC%24rIQ-Pq)XXZLXs5||+N4Q2
z8KfzN2J9?V_I`eSQR;Kod#Q84UMw2)?jz`%PwH*Dt856PCWM;IgB1NtdFe3vBKBKo
zN#)$O4aME|u-1*3Ec)JlQI%HN-qm?29`UwMocAnSCtrXlri^pae$D%oVw}eCoA?Ehnyc)F{Jw6j9
z*Q#)$%I>8v1uR`MHPUz_Z9beZb_v=-cBf0*O*Hr~E+oh6jXX7N>N+ezxB;aC1LyZ8
zwO>J(NbAU@oi(5T-NtOI@xc(m7JUMG7B}EzGG)%(Xo3A?BMIA;hYK6*R$MBFI8-ur
z@A4!2uA{ek*^R-Cxyoz>LXf!_gSm(5?d|=+TAcvuc4_0gcoKGZYIW!KR2?K&+J=YE
zjSC8XGMqTDW3E{|nEW8wwAAXNV|O|?kGR>Jd!>#pX`~aD_OJilPlCl48Ww*7PEghA
zq$ycVY*r<*QHQyTUPAVzkjS6u^s@UgOO$r{QKv()I=)T=m6#vf4zOU5rAlyvhsian
z+49m$uN6{#1G(pO`%D)?YEU7E(hIYgV1?A(*aJQ5ChQjQkb<9)`AdkuL;
z*WwRuJ{i$?y%6^A#ul?+;T)a)g^rGn>*+e?Ct`byZO0tHZi|K^D+DQ>p>K&V3Y#Lx
zK}Qt$2e!BHbop-12+;h|N=e$H`=!<2qh2FY9Mg?5;;J_nn8#XbG0joE+rlfXCP2lT
z^E+JaaplekE+)KM;~TFUZ3`RL=D1ZL-rf5}^jy)vBNsnS4xG<|gz>u)U}P~VP!%4{P}$#L8}x_SZio)eQfkc>VU3(;*Oa=JIv-o#n02|8D3tc
zF0ojTcoZjB4X&{6LIdB!_mWYiRp6I`MR(M*KmXI^Q#Q#}1hYc4$8u|LrUNtcdvEp9`ggDh-E9%@s(-g~aa(cP8}4sdR>W`=++aKuzc&nOi59)lChT*e{Y
zmdehbT7L9}2!`Db<$Q3;gv5m6dslb#jvJ4%YfSOA?@JU%BAWE_NK
z?nBXibn)x&dyf6P2We}3locrx#g&JB;SDv7(nfope)q@YbU)A1325suPeIQVzvHdR
zi#)}Xyn}AT0yR|m&um&`0v&`vaD0p>Fg`OuX&jja;%L=T<0l&Dj!7iAH
zF`+zVXKsoDwYupB@MEGeV{=llK>Yl0-)VreIU`l#AuZoqxKZ
ziaFT|4YTgcG|>;1Zrf?72^wps(fvLp+@6aou^auIIo)5=TCGQIHLI6&8xFX7PHv7p
zpF$1lyMAeD`#B1IW85=Rg%tfqC|CYmW|J)Z+hz+uOgm)EuxNjx_85~I1R;xNhrweN
zt0iK*{)6W$mA*0p!tbCv@ptmriP-pbv$i=3#5@+=Y;mHT`{B^k*}`O2!h;1ig#zY?
ze_JQw2F#u9aB3v)Gy2daY==lKs2-E+Z?nx*5DKGI)K7OQ@Vu~OC7jN~y6JzxFUAE#
z?-p&pK(MkqZA+CCd9@N*ZraLD4An0e-BUh>Kl}OJ!S*6Dgep`5x}pTv$sVn$l)LQ7
z=;^WwxH>KyWIbHnD(yRY_Q_0xZg+`D65=jrlgOyPfBIgHa=oj%S@Ysk$FXKs%eF7O
zjI-Xj;a%{4PfGr;xxNV8bmAM5V-8z%Iel~l6Bwey(`Oz_JgluMj;(zv~tn8d8UBFX#(c5#c-
zjhLPHS~u);sHnrz$MJZjt=)OFh%?fU|KB}x#Wa1yvM%+~B?HDt+G?tk;b~hrCygCq
zJ=(u1tBQ~%Bldx@+V>EbUj8&Nt;Ne}xPjs&+}-P9)Lt3PIIk>eGE#KX9KogjQUxwZ
zB1nPEL-A4(F1?=urtN7FgAl#(Q5g$viym-
zF2AfWaA0_K?IxAa{!S-5j90OyK*cMzc5CQr4)%gT&xGX}yBj}66E45|VZvtZ8OGVL
zQUBE=$j;i45oC+tw~l|@MwV=snpr^~EKq|2&8#BC(_CgOP6O;D&~Srr)FGapwlk2L?2M_?;d3AHA~qCq6ep&XBZbeL
zD;&76GEym0qAcyy^Pvogpg)F(hv%ZU`*$Q&h|nCeMZWDh*;MB6J>`0aDs#u6X6@a}t}-he
zG8|UHchg-0lD1_KKT99xk2X`aGWrPgzE*kb0$Y4G*Mwv}q5%?k4i|
z=-kZFTpAwg!|=g4n;JxwN*@*k?RQ~V`?jW99KD4xJ%ZsqyY|z&T^7hPfaYxU0JyNw
zUO~K(70%Ihezw-YeJSC0!Lbx*B*34gZVKf`0!Fy2TCg^!^<8}W8bqmI&WcTaXh7yslohZ$>4Knw|dD~es+`K
zw?KeIT#&|WD!npkIgWDAs6}8N;(-wiYMP1jD^6T0Iwcffwg4Zrefym#h**ahru*&w
z{Ie}d&5dePXMY(e4AHms$+o0v8R-P)ng_Dr$D&FN69Wg8cDHgTJsSgqbIk&kd5el}
z9Hp4j2oKK#5dbH{9cR34^W7bYv|4)$F_KA7-$L(SDN)zg&hHC#UAS&A@-#jd2Q=oV
z-%GMCRKDR&o(|mJTKxYXg6(`Bb%m0og#pu?(1?^K3ynw)K}OQ$!NhRqy@KnpWY_s#
zAR>6^vSB?(y=A+zRtv)pg0E4{+idpl0{p7;SiLlI0uJ7T+?Rlqj0as0Y(0sl>h~`L
zVQzO+Ki)FKryFwAdpU1Zt3&KuAWt)oZoHT<#9x>R|Fr&#(5t6$mpDb{bD92RO`gGZ
zWSvJFe7Jd_)a>-TV*qQ+5lXM$+0^#_wOXG4gPz$YbDhg1<{>uV7|Qc@SO_})^}W)u
zWPq^Daz?_1_^_~PW&wGu!*S`IEQZz?NHq|`U56}Ik4M4ZLJ|9C5>;MagZ#7ph0WQA
z3bpV)jGsEoe^UxUNFh)0F_0%2`(6Cp14Iahp`9;Jo1U}ln3=GfjBS2@aer?kLh`vs
zFFUwflDf+rf#>8GZ-j0t-oo3sGr`MaZg4YE6I2|e7EqB71(!FPFDc~WZ7!H9a&-69
z<5adhyd!j~i!F$c_o>HCR4@
zugi(iUqsxGLrdRp*-lo6n*UCI1vR-ap<(Z~4c1+L2f6W9hXcd+4H!~E`amwKYMJE1
z0z}Tjzhut8>t7YgDZf@9R{+7J%lo^4AceNK?1(yEW{1`@$y=05wU?g~H2n`gtPcK`
zu=|tLY}b462lipz@%xMgbWI$IFp4H8^WehH!wemNZwSJ}vGlE46$kb98_DA|Vuuw}
zC({Q0RnfpG!}>S4=tSf0GG1lQ^}*tWi~wm7n%cbg#vA|X=J$=E@NB;D^+{B0HoZ;v
zk}<$D>Ii
zwZ+Ga&bhwlM1C|U$Z%Mo9vV$-&!p$`kkaE>?*b8Dm3t^Jmh}_kIn*MXT*7DU9kCU{
zgDXDK;G*L{rwG>@-<#u>H+=$klE%fJgeA6;jO@udLu_&Rl*!Ekl^YRXcL)k8^DDIN
z&53$J6JXrPa4E9oPCVW?_WI+Wg_e;-!Mr6;|fmLwx$qe&MQ|Ye1_H
zJI2+^ti2E5qP!i<=_@)32Qz;re?#7O)f9we2G8f-MogEMJt9qR27jy&d)yzQe8S@a
zD*OQGs+n6ToQw%sH-hb($KfSe@D3Dq%5|l!o|J)kW`YMX-m$Mat(FcE%o<+*B;a=f
z(zsn);Qt;bL;hA<`vlAYFf88R;RAqDpT_{RqipU(;LU#0fC)fM895i3W)TNl^c&6%
z(<{s+N(WZ=DAPd5ZcBd2U@tW+=>2BAeO!2(*a3yXx>3
zHu%Q8%`xwG%BWL86a>g2G*80jc(hvscCLL91*Q}Hvw&M6pbY9Hlb{F#?4LeKjx3VA
zWv62V^X33G*CLzg8yp!l5hjwd)q#4_j7;ca7VJgEJkv?Ich08bH9SEOFpCiFY+(ON
z+PuZbBk+ZD57RraPje1^wKcgsPAc9PLbt@lhS66zbd%0EA2lrH2+h3U_h&-P#|bAD
zrgY=Vce15FJUi)(W3k8BP;NRBIYqoaL4a}KF_hC-N|gRE|G^qr{aZEAO8rD$)4n5#
zS-ZRNFNXgMwgf+3G<-eTH`}W|WWS`~C%*T)G=UL9`LXrMWA?LP=NGbRHc`wV&9ts;
z?Fk3S_QHfQ{fSLl5(GnY`Qld9o{O#OVu#+1AH{jY(!A?Mks%jK!N9>BFOqmmh83y(
zUsP*mhcVkIj^2p)8?Fil1Zs~y$#5TYftaJgqC?)l9vMfI2|Z}kd7adetJO+EW-pRa
zN6Y8gZNJwHZvdU$-0F&?cfc5(<(%iev&4D6zOA!b>#_cUCY;(o^3D{QmiIj=m-1mAvO&Sbs
zF26Ih?)>^n!Kb%U1pR$AG2r~TXXZA2S$~>UMne6jeETuL@s}O{96gh6hFK8h);48M
zmdPwW35!huN+H5}BPU+-7M@qdyycV9T`RJVV6!_;sn>!_Gm%vOTF5^a(`4)HK5=Ax
zeEcgF2Y;O2hl-2)Zb?FM1;zr0Mf2S{j_dDKFegCY3vO3Bu^blL^>U}sO_%-#HD2Sr
z5Z}S(7Fov|`do(i+GNv#@eD!ybu;bjpqg%V!(wf=v?(bc`;`#&>+iMhId-h@XI46L
zCNHL0kI<+Dvt+9x!!@y?gWb{gZ%PaJ-j%eK%9Z(xfwwd-%fDm++2-F)$huqk!ABh;
zoh6>M5|?NBCHbLfv&BF%Z{gk&VsOY7X4?-@iRt!l
z67HEFM!8x&kkz7!J08Au%UcD|2QM1J^?ZGrO;39gcb6>QohBFFf++2H=9|>CU*&$Pp*s0&&-n|n)E>@q@QlFR$=rs9zk*DW=2xdn+KfUIWrl9eN
zR0O)c*U3I@S3JIHK5-JS?yu836TO8NrFW)PJ+jp}mXuaCO7iQQ8kag1f#0A*+h2&C
z%hme=Na+6E86XqCjv@g$Bv4E{hrPEhXs08HBB7Js1BZ?WMjUt`nnjxw2-4-DlO8Lu
z-*qdfgk^yc0)nx|uHf<`ez&RG@mNOn*jTIK*mmZ^ddtx3r)&g0&y)S8{OlP4=o5{c
zStsHK1q@fdGgI%IPE?b_;>&IQ!Zb#DSIk;9j3(q7(Dw~K5=wzs8H{eQy#INDcm$(;2hmVd*GLd!xMfgV*DzxCN
zLnfsvTi-;`*AZTrokHc(2>ZAX725IV?>G=l;>duRXg>tKg2v`nRDqR)la!>=%;s1-
zX5a7cbxogundy&kdf227=z=<;OSjJf$OC11LFsh)R!+U}18D%3rb$$uSANf}x4DHC
zZ#E>jbh&M+3rV@Giu>r)0PKXafaTGL*~Z{7=@T#=U6*lhL9WZCL51~h5jvb7G}GM$
zpP#vP(L#Pg|8atMf04d3IqeJo$V6TS#UeXNc8+=1VsvGsA+xhBR-&^lB5%ZinC#HW
zwmo!r7N44t-??
z*p#Y*S?2?&&svz42KwUt?8|Y`Wl^Nmxd@kz+=*9O4v{1t?YVwN(m`g%w_d^GSkwho
zKn41cevI{euU*%7fl)cLwbAVSmhX6U{uYx6+`>d0a7<1uX;LD4i!(}>ODKV
zXs^{i?3D*8Y*;fQTSK+W
z*sXT93^AsqmcaBjU8v>fm_-R~qg7eZ(gzPV*nEw3G-g|rMS=(2)$}pfb+AHgtaQGm
zX2YhYaJDjJWj5u>h{TFTNXY(ttJgh6`5L(<#gb(@w(wUV!^v1L8??8yz8qzm{_X);
zr?GJvc-+B-T%m#)Xc4+%TYcMUc`bKL=jz?f{aeBij;9I*xvaLX3>zisoEui##=h9c
z125efirWz_0ws1&GL-I?-Z*uk50(N<=KSI$Tos-eZQ!iG!p_7!19Wr5!2H)3&^acQ
zV~@#OKXr)nvtgGuyr+jWZqsEZnUrmOXtRYa)@tZFULp-~?`1oST{3Swh991p=lmPt
zZo5Dn3Z6-SBKEfAIGn}u@yQej3Eek-EQ+krqarSpsT-LyI|)gd#2CeA^R<(TOhxi!
zQ3=^0epb4F4sgSp?P}=_ilI~6`^%r>gn70qn=pdVv9{gGHjzHq$L~@8ZbDogL2g#}
z+o>r->7V~7?e6YY4qawXZJ5=vx^sQ~cjkQGJEq>2HW9XmWpDc}lW>^lR6Rl2sv#+P
zEGrW!*nQq9(jhuS?dNjo#gX&J^B8-i?wy*0-pq2mi;+Pk@0pNia1x_DWF(*
z!}RaTS4^dH^;`HR7W#FZj7z{gfXhw6Pri#{%e9>m#6E8HGt-1+e^D75d{OACaZiMn
zE8S2+KLC-oR%$n1;u|$&L=J`SD2$bQfBij}#6%L4vQUHSPS4l+Q(vuiX-fPP1FspA
zwyB0Fb{OCJ!Cz$+7w&1lC8%wER14RmK)!|51D6OgzTdLC#F2M(mjNK932Dzw4nJ7v
zzWFa)QN{;YvS_%l*6vRZX%J=5^R(+Fnf&j?J2^Hbw;Kq`n5Zs3DdkY~Nf?mB#pjT+
z@qWipx!{0@GZDv%N@JlFfqw!NKez@o1nsv`10SY#S!Zw?0*Td7yc?UQWyJ%d@dVf7
zfAeFFUgzaa#>VvLL4IJ!Z`745ysK+7_Vq7+Y%Jxqx3l0SLPKvstk;a8rK?GnADi_e
zTz-5R{4v6%Z01$$7D1e1?!GWQvMtj*`XL`hymfi}nxnORm1yylIlb%rV!?j1tUu{{
z_cyn=xijprbiM3>EWCQaR2t8J(9;ym*sx34i`ICNvBwECMxZ98G#>0z}ZqMql!31u7jpgq*xh&Qw8{#JO
z+C@j;vip5AK`c%awz_
zLz0iv2A2|ie}I7rIFq}IVlNiu&uec!9rL%nTU_{L6J^ZgR7$Q()CnE9s~flUN~L-L
za~kw`xjxb2bG1-LlHWaUZ%Ny17lOKf@0i5<=W}P>HsvPvTzt=J50D2rvIZ;$X{6o@
zJ4>1p69<#MwyDh~uQUPqolXq@kyOt~w?dgbWkT7C7_IKsxSCp^dmOB<2L(sy3{A{{
zw*!@xc@9<`8@>JEcE
z)zz~N9%0pmnoKCcf~K$Mv1iF?ZP@DTg>m)jgTAr(=>E17cQJkzG%e{Yw*Yn9s}n9x
zC^1O03}IGL+1%=8Sj)X?wesEEwIK5;^Fz7ubqn9x78+TFaZmT8V~a3qg<&GopWhNl
zM?MV>NgTbkn=(}S6F$`3clmT(=x-K$;JkxSYuFRgOUZiLPe)T<_1U(-g`?YNl2_d6?hyelIzF*r=;j
z+I;(0sKooKFHLkT>s-#F*7xC7e~F|9NCLVDk6?w10AZ2hMb9o+fH=pMif
z`zO##?=qmwl{?N}JFQ3`lbuS*@Ead?H*5H$H}Xfk%m%3X39R3&;|HvYa0(4oPi=?ff95%OQo!BQ>QdHok-tunKd7*Yvgw
zeY=lu@~-5PR`zfhEZ)?5<}_9B4pCm{7Sr73u(A5_&H62~<{rfi$!oDQ|XUT}n`q4nTI^
z0S-0^n3N*_9kTf@C4Peu@A{1!w-QuTuaeET`WTvu%uDgq_>b9Y0A`zgoYaaqRQ`M@
zyDa(ctEh4uy1S+X+;}{#M3S&j2;>gONODq1e6W7rm98gnvv`YhK&RkCQ2|ksB^Oj$
z2!hzBDQ-T#V6tB@g?G7`w4&x#QkV1ccj;6eFmc7BtE~6-VUM#Kf
zQ{^W3B=qhp;GP3~urq6;zh+q@C-z%>a(LTo|H1tU&rkHF`^?JD%hKLD!f!ug<2cfX
zlSILj@Cf44AJdE^EddfHRw#o%gixl{KvtZ)()s0<D!vbD;42#
zETD)dA-tzNYJGLPCTR`2+)!1j4-0;yA$VU+IB@*X4!R+P%L;H#pL+-x#hcL6+=4B4tx*A1Q3?4@kcAsf|PCfAfKYf!Mzip?gFRRw!{3Y(tbL2qqc6n
zVaY)Afs-aI8J@M+SU`u?Hfz82dm#$w6F(am`>X549B?(?d&qE_ZVmS_={u|e*PnzT
zp9_g4d2qpOl{`%ZjYUI%PP6jOh?GS
zRk}GA(rxm`ysY%YKuhUKSO{b)@GjgPfQE%9a-L#kZx8?;L#m^qR?`aR6RuM~DO`KUKqSZ63S`G?1_{JHB
z-4!+d@j_3X2fzI;MQn=%v2ch`k-nYLBjfcrv?^J!Y0oV+n2E&dVWKAq>2_Vhbz*QG
zb;se4C4XOH;{FW4e6#Mog8`Mdo7DYZoB5m`KyXF)R{|wIVqkvdj>PyyuyvVGH||H#
zN#hjnoOzB=iIiqLCin!ecI)bzwBjD1zFUC$>Zn87rCfGsCXt}bc7nIP#dYiNVG(}K
z7O`kOCKURUA+;oDLmGF_IIjW9qe{w<#yz1WI=f!Zdo6nsdZ-*qn|9C)#xf?uzc;sC
z3C+A{iw#))TRvtLw@$)by*NXGK$M5E;dnLIkxYe5~IP-t$>USXy$=$56Hp*-j
zGp_tuW!P!_%NAQz_2R3sIf*sy?IrIt&q5Z7Q3oPr&SMcvxgzqmg@z>fo$-rVVOeX}
zvip>WHn*C0cdKvo9`-!VOpbanlrWqrv$LYD!hI>K$SDo9JJSlC{j|>)
z^3Fixt7oV;kHZ=ssT9X3Y(#WuEH
zwfk|)w>qxpNtaHyXRl
zecxkjWaqubN!%@Dn5o)Ta>q6v64(6`K9>)vCOy-MFdCmJ$kbQ{>uY**r;7Q0$qC#E%mqL)!c>F+#JRgfcyZ%Tw^+z$mpbi+=pw9N
zQO;Jg7;f@?`K?gT?Sh$O)sp$=3BTvx5aBRyUd=s5p5!Hr>HTaA`nOvLI}W!mpakgQ
zBo!^Sn*!(i#C8|6&oYB-BZNGtzOoqiaQVs^HV`el&-{YtnlCqMyM^*PUJU2QgO$w4
z@4ORYvZ1srKp36!oKDs}WdVD;Uc?%>Et_rJwxTrQ)@{04fF2?kJ*)OLq#fS+^6bxe
zbfEO+Npi37VgqPuw6_7Ro6}xat6-|N@BC#&98pbI+FdIO1t=ilrl)$1%kenWGoq>8
z61nneNdPTPslC;;vmSw
z1FNu#*?m8hYpp{Y51Q=fm+a#Nj&etSdUOV|<;#K^{ACf|DS-sPE#3+ppER{vcVua%!&Jf-0feIOtWnK3^VzMKX1c(h>o5*nvq
za-Q`PD@^{vE*o-`%nK;+)j!J!k1||j=IO9k06$
zu;!EVplYkW2YHPZa;)LD_#U}44+L2di3WQ!8~fWMlAv^}Y0T|X5mO3OIiJR}W;Lk8&+*HA^+^=IT%>J@x8{V4(~
zf%IU`wPZE&;5<7PmmePf<qzr@v+;poqS=f#imz}_+5PE{(EpPg~B$T*`N?du_)0Wp`tq=E{PKq8ngH@-9aZHwPA{o&n=G
z_`+-t21>&y!{%)k46BgI8-`27TcPWa8+!C0^PN0?2=A2-v+LNvIa}KGAoAi5`2Iku
zj^*CL`sj+{FWEd+U-HJj%WzKty0Q`7Is$1WOkLjF-5P1Yhq=0ktx@~h6RF^x#tFnK
zdaktKuw`p=YK>iBER$84Jexl?i|Sok@tY$$wjrGIf0-E7VCS{FKy%*F=u})$6S4!O!((VPg68SUa;`pA)g{vb&`hER5%GvO@c_lvhC+h;#
zNYM}E#I^7DFOYT-wfr&L+fy5pulv*Eb2RT8P`j`GThtHmNDf@p!QcuD3(O+Ch!Zt9
z=M9+P4E9~uY3w>bESQCq-xQ*w<{G|l{p;P}fu-O<_pj}1i=;hzo>9mgGl;K1>cT0$
zyi{6tEC)LxJBIOj0;_WrRr-7W87S-8D~`S^#-iDMs(K_S8#avMjs$+PD08p^x8DO#o{_;!ASTdf(c_VyF6gPki@0H@fiD)ojf!Fz2D83k#z(Q?+f3I0
zuMs^K5tL!e_pqIa-=Re_7uTG`S!uTiC?Ai!^J9#THVZC(P_6z$Y
zko@JWD9*?7xccWhP7Yy?8cxoBXO_Bol=r7~Rn%qGRsOYP+aKM&a13Vqx{}{bDVt9z
z#BY)nP*wl+VTCK>>1`tEv!e$;cv{uCVGXh91O6D1vS#KsZrFi>Q1eYF;L_dG^HaC-
zbG_w(E#RUSm`8l^;@RsXuK`!q8pw^Rp|uz7>@I1I-n3?wfE(3wqB8Os>s9jS&ehTu
zRdA6rNjG%YHR4M=)*2VyE(4Jt8hJ0@h474g@9)U~=kn-s^`WHg_Re++Gv0f)L;4u3
zoI9HEG1FsB;XFiN{yYRx1t#S7O&uwx!A7quExS{|utlEMnxbr-NRWHE-0WccNI7qB
zK?R_po57gmgQ?uZ&V@s1I9oxVJJMN}yOt*Rnrzl^cj^z|M0W>KP_}}{vU6Zq18IcU
z)TsVwUKD4Hyllc1g_^mdo&B|X2~D|d!4HDj^7L!)vEwkcleiPOzd`XCUS_s|x2CEp
zWl;NZ=4F5eY{YNkj98iA;IpVy$d9$$t8r6;scuajRIY)L9!V>$+~bkNaKjyN?Kx2e
zxk(cxU}~DRZM&q2e*5>2t4HSS(?nBqF9QhF(XFCFyBJ%NpKJ@V@XRiG?`qfDjP~d1N|DF84
z)e&A=&ics3moPS*-?qk4RL`F(9|*#!gS=GC3KjuO>_6)tuNpZ!K8#%pF#fkVGJ`odQk?}N7nUbAGxc@Zu5tR&|6p(}QmLdOdLFIyvY
z40hy4!BO})a~A)-rsiJLwSKJ(e))W#n-~|6ZF_GmxUBv#x#w%X={jX$;p_L;mL=JJ
zb<}wMW3c}&KtQT0{$7f=L!jR&PfO}M69v$`a5OZ`zTRR@fZ;hH;)I;fD1`gnMF6@n9VL}kMT#A*tDbMu46czN!yCckc=
z(s|>00TcsBE^dLpwgYI!-k56z&C#7W=ss@q
zp=tXT`&5Gq=)P8>Dy-pMo&;fr^~hKG%<>r47ggSN#o0dUC?-+c=H9VAzaqRS3!JSm
ztU$euRh9(~cm_%5qR817C(o@j{{cqzSb!OMZ*)*F&5DV{XTX~>|5<=rKW?vraYx`k
zxJZBK`(Y8f*oWDL@A*-zIXv3Aim>CCttq>@)b|;Pxm2oSYaP;L^6Gx%ZbqC~FxGUn
ze~N2Gd#+WXNlhs0L}GXpQ`x8arfVBVJM{Zz`Pc8^e6;3()BoAq-6tJp(s2!?
z`-&T)|3UT+FpJ41v1YeD3+D2nw1{E73Ctx)eEiof{AU5~0S8s_ABWm{s%
z@zZiy4rKyyc10VUF6xe=f1pJZYOp`y46T^&DCuFw&$-s}D2Q6g
zaUUA2PH~kM=nw`|kHa^CX>TB0EY=MtvzF!_O~=SCbL
zTVh?ZnHuYNfNb?d0I_M5$XW4P=+gJ&PgfhA066j2qo>^g8u8u81BJoTK!UM*y<%{s
z{BVF-Qlh72FYXnf@cxOnh{DJ!a7O(?jbJ`n6qnk7N6npg%_n9pS%;+cd2LP
zj{H|l{`*aSZmg{|QvZlVRj+I(9H)A%rVW+fYW%$-w+m;$l(sV3;(v;C$?lAI1NF;F
z{xv3D?=KM0eeJ~Xa4&AdLX=zbgVX)BEz4eA8%YR&3lU
zHCHDMge%CFBA(c_lo;BR8YFftln*4%5XR@j>i=?zf5owo
zFA`*L|ze$zXdR4Kq^bTvQq8Sp2=9
zSE0^vs;b0nia|uID9`c34#uu+S8s8DZk`~F0BJBOI`$dck>fcPQWqUqW6e~#Yj@fm
zW6HI2#R~h1cK!zBf>3m0?XD=!IIm-|A3JZlX`n}=!nC9J
zyA8TdHq@86?$(u$8Ci&&Euoq6^A}Zk3l#Ts4%A<&XcxQx$CW@5Cx@#yc^NFVH5YPS<8c@l_$txR@mqy*5$AB
zvunWPU`iM-I4jI~HO={#cn_qX6)(~@e^A<1+l&Xl_G?f0#@+qa_r>}yga=9`D>3Xq*UjVSH
z1%IqJ4=K*=^MYW+UM)N-WS*aCkK0&A0`HV`d-}g2eS)!$ZWf>Uukptga;x9Q5R`X*
zMJ|=pP7;UuEG%8)OU`|^2n-d8j2fH+M=YHq+B7O8_oahZ(zI%KFsAEq`?$wjuv2+B
zz!&<>FsqrX+#oAs-hlXnW=MN|!mm!_!c_V{bvxN?R&zc-UFi2_poBAx4exh^bP*lA
z@n_B{Y(Q~8GjQ@7n7)v=S5Zec#Y7Swh|GUgHP0bi`HJY@SfF{wfa3E
z+uQxW55waiAt7P!xtf$yPuE`(U;ITW;i1Uv4^0>@
z6|$-Cbw!qJ%ucbasNbN=uk?65;wH@SdY%Me7zgW1N6Y>7q8$m_iN)73%y=_x?ppfd
zBNG#K?n?!frFgNzu=|>14-S4GDl-V~YL#cC?hko}L;$ppRSwyN
zN(c~I4??!dMFht@jd-F>@EmGsF4eZD6}gB>T_-5*?Zxy8xKvO})g
zgoJ3&AHp|G*@n6oRhN2HPm=h|YWX}{b{$(NDz3i+rw}r>QetVwq+~U50^y2*Gi&4n
z(TR}g$e~3W0I06Nnh!D_rG%qDChTMPY9EYG@)lu<2M1UG>O#YFjgZ@1a6{*y-k^}H
z##iT%u$EYK5w`Cc(aCN+j;O|}dF3{@abXhZbmldm#fsBa`0T!mf*e=EoO-h|yE7GJ
zILl#nm@)H8$2l4$6rp6_@p_N4vmY&hOydkMS$E>NG9bNK&A+jK5Hecjyjx;BOO>7s
zKir=|PLL5{l=%gzpsXEmmMOLKzk3JHVJlr3EK;gGTLNqxE}cABNuRWJ&7@S94u0aJ
z+feMcyy0k3IJACUXF7SXzs0A<@C4&ndDPJCchh(~_!
zGyqgwAlTnH3?Qr`8TeVZ2ta|D5hHz
z|J1V6GQDza+l0BH*tNq=zK|7iOA@YNowTy@W;t5Wn3
zroonCijE=inb0WG-iRV;!ceOXGl2P5q%r<}ii?yQJ`4NM{betmPsxMxlY?0Q(58jA
z4{oBL1>EEgG_JeW5PjGa6W>2eV$4hl0C3~kgUaS9Fb)@@a}BOoxA5^iEu*t2=!@eb
z_)Ys+yHpN9LEvgu+H=`N%-7R}O;g~N*+8wi9IF2jnyM9Rz?G`~YAWrM4bA!J8D$go6zjog?ZG7>6J1p1DXJ^5H%R0&P|A2mB|qJU1ih2Jj@k>OWP=ihweB2;
zHf)jh!fyLHmrHtE23(E526sDC7+J6Ud3{e&67*O-
z#pY5gO;Ds|Fpgi+m^k@8E_Fxoj}!90AHvjLh@y44d|E68USbbK!>y9Qvpd8=Z!xq-
zwc~b!xkv~%EEutz$tHhi$r62gu!I?3$1Lcv++Q-ZzxG_)!E|Lq+kJx9Fsu^{Ls%=R
z1K~kB>Hcj$GYlK(C9K>B)SQd{d=s%OB_1+9w)dDD_5H;}BJoE1Vt{h0Kq#T9W&6JJ
z6+i2i54PSbzg8nGSU2i8ey|21mMaaw8~K(JOqZVo-L~^&z6>V^#DH<{0tL-0&PG*m_%XD8L91E6Wk&}Psbtgj_ZJWq3x+sL>O&b>(
zk3(I~nMGAF{~qEJZ9}0h){@1(jJuYrgSKk#&GnnMvC*Wp{`~qay*=>%y2>tF!tSiq
zBE4S(+COn*?V;PLf~Et1bYYbb(eBG{*;HwZ0GeI6|*5p9*386
zqBz4!3;I6w*`ZptFY=qh78%3uh&R5M;``hcy+Rpi&Y1@P8>rUAT8n%6M^jo1Gs-*n
z56k(!$FWI*iCKV`L#~;yrv(jmQKx&)@v7U1-%;L>`oB-O{~wygT@$5ti4Yr0x=CVi
zJb8Mn_)-=_XRtJ-&r24wMHsVvintso@brrpF#@)vfMHnO;l7j?%KFglb?MmVi>g4=
zor6vMuQeUyzwyTcOdW+>j*J5`7L{|MhQVLX+Ooo1wnliVc0)&dxM3|@pNwn4&pIOU
z&q1j-T^F7$eI#B3cBiVa(oQoM78q{k{=sch{w=?V&}6nc^JOYD;!IoV@VTqELWuku
z&xNui;?V8X?*GT;x6)gSwy;BmNbxK$|08q$rD6q})q|bh)=P05i%1zYngI(?{L3ba
zyt!hqd(3A^Va^5$K6xedM?-J281Axh`y`ZyF>;?BxS;@ocLZ!SPG=g{SpjdK1VG_PC6kT%Sj5dTd@`2ARU!*~C(n7=s)ngd=FXESCLw
zU9IwVolnr*d`P~j(b`4Hsd?%wlL(k6)Uo}g;ofDWyZBZD`}O}CJ76OMX}c4TKf8XZ
z8`M+7Rm2_+FO6S=ox=LH4%W0xx!O+9kCl$u?+ohyuvX%}l-uc!@MxZ{4tD!F9mgN6
zi#B{naU~q~$BAQ(!W2Jc+Wh<*dw#gHz!igHYG{SAMAnSqy&tR?Gu63e#OZ>Wi)owq
ztCQ5y=}H-J-nmGS3?vZ__ue_O>>fTDEkK*;Y^Ikh%G>OJNtA2SQ7aC*IA!K|B?H#+
zQnP8?)2jH(v#z)#Ghme8|Jnu+N4J4@1ksBnnpR^W%@l~vRHw#5`A~9{;ekt#`?88o
z;^N@g?u-Fz?P5$bwvR08Nsase*n97wrq-{26yyLNir5gP>hUNN5Nv=*35r-iijq)7
zh=PDpMS2NAQB)AI1*AwQ0wI(LNGC)^KtZ~pNQu%yj}RcF-zS{o`5xap_s+dDzu(OJ
zn|bp`hRxpD``J%f>$5&hS(
z$cgvlCSxP^aQiZ?cKo&4kHy*uwL0y8&3`DZqKSQd-*|86d?m8orfj9xkuq&S_at>B
z_j_E!jFITY?a#dl&)zA=5l#i!N{2O9yEmh)d`&SG%Q~qs%EZz6hpx(ve8^{(?WXIW
zAK45jWv|E$*-qUbf~V|+&l}J-*W-eJw-<$jW!yV|dVEs_n^ExC2-k;c4x4wjl%~>-
z8)zl^-ydgjs+T0JFP;2g9P2YmV~0ZLL%M{`Qnl+4{X35QI!#h(x$)>iC_!Yo*FaEC
z4%3t%?S!CJw0zfzb*Rm178TlKvn6!DvfmEt-<
zgVP(k6oH{c0iLAF51fgGo5kw1ID2mRW52xDQjrFxqxwI<^zIt%O97O5-N=1<7i;#h
z)JJcT9Z~tN^`fi631FIcb+CeOZ6aF8NN#u+?%MM11wxLzyDsRG{I60btd&Z?KR_Rm
z?eX{;{Cy_|yZrlLNnyC7ZkQ@!_VD;}pzOI2bgg*eWUN+O4}`zP1zMze*7`A+uDaQ=qk}J$vMqvIzX(^BB>h?XVE38X*-VJ}Og@_OA2$bE&kt_xIb`
zl}Xh`5T!fL!tg;K>S0s$ut$43Lm#zUh8+CXaQxD_SK<$Y(pVwh0qov@@N29^4
zMGTHV_MS7XpfxzYnQC~}W!Su{r_+!R3M8;2$4?Hhwpuon?lS0D)zUh>bX?VO*@#?o
zt2*rbl&{jxWqGB20dn{9!8T_ljKWQoQoh8twrS93c)ywNXl{Riw)Ryb8mW`1rLgL_
z@tzG0BOarF)Qd~Cr&xzIOeFl$%Vb4bQ!_6(Q?tD2$BKSo(2%`J#lp#=C>2ac94B{>
zMXI>Id+7}YHoHd-4*r#;A{EcIzaPpSdV-Xki(STWN&s@Dc0odFj
z4K0U<^>DblW+21Yb8IpSPgK`E+T;~k7Z*kweFseoS-b^Zsff9fAfw=0yje!MI8@b9
zGuu<}nd6fV@yC5uk^iv>foV8%7!@?rUI}l{fQ7eL*2T>rDjM$FuR5_Lq-@SrU4Wz=
zHCN3ZT(7^9uuL!B6^EWHewn6E*n;HD|d2Y^=sXF(?P
zIJ+EF0OVC%x1$xeW~akw(-zW#&)wC*?Y8`h`v}m?-=8xr8FeN3z8|72zWzBRdeCQq
zc3dMGUi_v{)KuvVG8>w>JFEtwCotm+-B!VFxJe04a=^GO3L4B0(Pu{Xgb*t4x5rVX
zjf%J5Y@jdFM*7u%5n4V}Mt53%9o$x02pf!^spQ7ZI71a#raI4W4#ZVvz4M^Gx!r8D
zs5+yAF5)?;j1z^r+;Lg(HO%U@@j}&Yh~m|er00DCouWHYg-zidv|fX64W*g}lT(J%
z!!Yk2K;BU?bTp@{Wt_TB*fUT^}#U{`cjivK_&LSxEzrPjmPBEHSDnm
z{=q@u4^&tiwaooe%dz{57klFyOmLN4fFvBPe6<0?V}kFaEQbz`Z_Ll?>QPwW+U|mH
zJDH6Ho*MxHxWjf{n@Up0ZOVCK|o2v^-;4Fp6{`*+=N5={Wz(0&wH5ydY=1pjwcX({98m
zyLT`9c!nxkEas4`F1m#Ur(jfbFX@jzh7=~ppf9+5x4O6oZtcQ{`IFBgO@PCA_tJLj
zY%`Fj`$p}bg{s)D*SOgj)WL!n$uFaV$Mkr^OLojUX3(^BOEnZyJ;s@|dgS
zn&aDKf=oX2$S?Rr21^scN-n@<-UetScdL2cZJgaW?CX(()>aLT53V0x4sL9;5q-e=
z)?I4oYkE1fabLvT56G~LYEJk83n7Tcx-Mf=&(HJ5MuSc-)cr@o8be0c{kgLKhx31x
zC@h^;^Ab=-qPK49Zq!J!_WYTBH5UVGubnS=b@PBUtFf^#!ezffmnOVj_`jW%novjDO@e=$J%L<4chdMxBb#+ND?1pL^N?a*qx
zzQD2s7BG;aFM|bcZX6ea>-}gr6;r1%w0V04tKkMj#F}|5+A89a)aPTix*xiD@vh-Z
z=U1RyBC3r$;lopBrD*Ut8Jp@NF83Kp+6xgbuVQ#?yr>edX7>AOB_G=ZlZ4R|_4I5r
z6=%CZJ=!>nuyFz8n$_SXa4@3KUZZ%u9!tp_*0RpB4%3gjM2UA9IXz1G)f7~aL|P*^
zllH5R%p@10oLS;f#R1n>$n09Kdd&%h#EVPD@E!^MB3}12?$!xI_=STcwHLAy$4MpQ
zEu~L1;+yB|g06w&qI6g1;c!*^Iw#}AJ)wu)TH78mnr%w)NKQ&Wn<2iMD1g0gDBb@2
zgOKe-9cfkUh@XEX%}dX+QOFr6zCfst;L@l|97%t8J7+>B=3-%m-!aDFI5
zq2Xlm_!Sa^Sog~6`cknNc7wsnM`w$zv3D!aJP=P@t?rX)*gXF=Vd;}%9kq~S1Y*t&#?Yt#JnfA&Liq>@+E7%xG`DI%*v%p|!Rb2RGZUu@L
zueWqwnDji4sx3cRMzFYouFsdsLG^XK7`pZ3_AXIJ$KO7f(i->Q^*y+mtm+W{%6{{5
zGU}Kf8Dx5e>z&5aDZwBlXR@8aVa4JXdjD?&JV9&f%`Mbu4n5n@M0m7vaj;$09u%GAs)EsvhmTIQ!+&*}{3K9`pIX;kjh{r*8o
z>o+)k2wKn`(FM=%y{gPxd^7u{yM21=NrxXZrXU0UHbcTX+>!f>bc2uCNZbgVJMyj_
z-+8H6
zZK6E?!3AUEXEN*DU8^EE%xG1y9K!3a{n5$Jq-jzEt(kc>TN)NB#nTJfW3&1B@>QXRH?VDNILm(J?FL|m4>bY|;VSCdLT!EgBWXY-c9Vw!^P2uCz(s)X%Pi44w?Mv?Whk9>A
zeY(b?#R@WSPAw>x`ik-pxj%+T*1Sa@<*PObKd+U3H+$J_JA7v{hG{4cRY@A($x`_(
zMbE{(e&oZhf#QtYkU9!<4?R~r$(5FC<9-%D@w82;y}5z@(C^T{)hVwt39A45Oz(#n
z6{J#cXK@U~d%;vLlXa(9DVCGd#Xax)k~{=wiQsk}6NJZ-tO|cKFMhx@6oH|t=cE4!
zu3nh1PciVBDj9E}nKKz0K+&$lMITl>c;AGcn>+s2#m&WOC#gUijggZoFLpzF+Z0`d
z-!T$<=5zqA#db74;9q%rx>j7>d(wHlW9CIv1(AuTEgp7VkVqV!xw~n%E@AJZJgeM*
zWHL=tZsvk_xXphyP;&fSy%vr5+m(4#rlAOI_v})b$?M%^f`8Mafrl=T1WHV!UbB@
zQw0GP0&Y7$xe^xlh
zv=Y=-4Bt0c0&3a
zyhdJ*a|;gVC2M-f-Oh2|K;}}FI7e#c9uZwZOeytCOS52KMLcloTw2CnBt{q+rI&dP
ztYikEi~OgBZ#%L|t;}1gyoGl2Pas`&=j#r;uphjnh?f)bvA=mO=uX_&C|#k-q=m&I
zsxL26;;uNbIUg9#DnWw=b}O`|!`=(CiobM()GXVf5H;#{M#J*?{LOv#s3y%&JC8?4
z(s2+7R>W7B1hk>`ol^=5rePcd7eO>P>O$60#16{}rejvjS=Gqh;@B?tyrrGi+bpx)
zoV&b`z*1FQ4eodtHqR+bPA2Ovz0;fQlV|1@qBSiMwK
zXTa-C9E-<ZwX+NSV$n;j
znul(~BfY-dO2ZghE)=Dvs=@lj{z)SGP%Nkx^|}7YK_Iw*<|+9X07)bshn_Sn-7tXle^P)or%X-j~Ir;e*D3OL`8mU>lGaPynAYJL~1
zTc5UYc`k}kU{_iSD$wfbQrP0p(k>uc4PJ1s)Sq~Nt23%z$$K(rynUh$2_~(1@in{3
z$ylB!cQRMm&4xQK)sMDuKu)gwI684-PhvTvifvC#Y7eRe_LxHKJ9sLYP?`Kv!4$>y
zf3ii!Faq=D(xA(T3-sUO2}-kZ=JsJU9kw(*t3CJ)Vvk}m78U>}0mrBPkv^UI9;Xas
z6715lsOH8VCBr5K9-*tr2h_Kp9UwEjr-JA2g3V9@g769w%w_!Tl(b>8@YocI)7&P(
z*!fZ`{GmQ>ga(`QXT1!Pfy3QWk>*B1fucqhdduf>FL)r4peB>FAX?_n>YM4Rr7`Y>
z8*d}ezYCb00V#52sQEn1^ubmcnQe7YK;V##F1jiL|9)n!olbD|b`u$`|N16M1O^Bc
zHtQWJEFyMW%ef%))?-B;1n+?&9k%IZAMY`QTYTb3ZP4IehGdCFx*}giOQP;XitS8y
z2W~dP<}-TV8lv3#X->A%s`xI-5%Jd}JBnm;6S==og`c5EC!k%xE(OsZvUi%9CMuC#mItJT3T_ppJ!Kc5d{6PZ&Equ?#ebwM
zbbfX^$Gg!e6W6AMddhG5^piI+5dE-j2Mo?NY})xc4FPJju<(8wALnaOwz+e6inm_m
zY$S}vca4atI1J%EF{ooiYAme*qauafFpU2OsYA@(
zwFK+C)V1(4)!3@~qe__mFU#DfVdXA|5rk7}fLoLz}6K37*M?KCsAMhUx
zk}J}ZH7(o&hP%|E`b7FXlw)Ib%wf*Bk)Xe;hSOG4a)rMlEWRniHe|AEZrm8(9|4Fg
zTan>{@8PLX1C2J!iscy%{nY>3!>?(%GvvxfbJf?OrCi0&>#?DmV9UL5MyN?#C~u)}
zbP;;{5%l{9PlWb(n1w#=(!xD*b-)Z@2iM^YMul$bMdrALbw%COqm2$&^c1RcQA=??
z3Mqtx%vR5VaxccH*dvfD`02~QiT(z^tpZh2ksmJai%?X013#Yao>v;3+Pm>-TUQ-0UXb^XUeb
zl1LiBg(0@+;h=tL8yAoZ%l!qJzac_~LgY54#De$)ZibYEDs>8s4yrWyKv#Z6hdutCDcZUVfNPzAvdam#xMbleNH|kYJ;b$e3o<^A8
zY$dxn6olc;`~NUE#k82b4m(DiAO*e;nCVSSh^5onQ|qFC(KiEO+(1J^_?BsC0J%d{
z*C$Fx&%XiUK*E2{Y%nzmvq}ohuk3}-maPL}Hp*Q>eqUc4(y!TyNt|zwk8hwubhD(1
zzu1=%6L=r!V9FgraTe-jptb17#xcrGVePJHtD0hoh0v$}>74~UQc#Et_
zBjB~p4)>kuYB!aUoPt}7(0*atFpT&WHb0VK9qu@GRt=3Wy3iAONM9EoxHn(zhQ^Ha
zMsn0IZ6zj$iv*tPt)aYmra$&8^jVkdQweeb9L0L)9XJ5%e&E?DdUeMGA
zzB2UQrpqyw{MWe_*VA?o+x0c{0O-=lWI0bkctPsda-=9v0K8zNW5>nN18@)(1zuS)
zC(?v9_Iob)Rb<^JBOHzn)CT`I=LFGmnfZV204Lr)p#?$<%km%cJIwnvi1ZGPNwWec
z49Okf8L;zz-6emkk~jMTAFjz-398e*j6v2n#`X8saa+Uv{nf^yd)FQ`slE1~
zYnDj!yP9I&p~qaqkN8<~{B)O>N@Lm$=%XP*i#rS$R~;61Y*V}R0d)@iitW(h!yi(i
z&U9vKO%Po@Jz2+NC7nrG8GiMt|955Xftp2JeyNb?28oYu{6!$}je0xl?pi}hBYuvk
z(bka1i&>b|&(I}<6a1+NI^eW8nBO;c;utuX@W61mJwAPpdFKkh)&%)*8P#j|x#4e?#Eifr!T{AHF-;Wzdw$EdCb4`2
zdmhtbz8Oot)c{6AzbXD91j)@#L?j_c?VDWbgFz^*D~Tif|7&ATCx`Dx>FS5
zwMt%|TUra1uc1pUpupsqjmcl6aw3?F6fZYe$pSY4O-?8lQxcT#>lu+kXfj51r-PjZ5L8Fs0U1_+Zc{
z7n|pG6^>B$_tPnDNHV8hb^^IL_{*475
zsf(KF|DJadDG7T2vf(C6h0Hn6BKHfVE?|32*w6ak)r0TSxgP>Vbabyy`pvRVn#QBg
zQAHrse4G8WlVSEj&(+=iIc6!eND3~W*Y~53j$)U3f)dXCZ4NahpqlGe%vq{JfQ)5G
z?TsI_Nw<1DzebX@QhdZf69s*sF|;IN&W;xr&Q*aK<)x)6{@f>wntUIM-H
z7R>!)V?|-n+m3fEN~_8$T6K)=gbZDf5yCxsl$}jg5W=PKZidx6f9;W}U|ko#{3`u(
zeBnhxP9+f?iSx7{*#p1xa8*8szS&1@Q>vb?%E{)v~}j
zca{RO3
zogrPqDT2bQo&8=xgJ=h2YgzwY8AQT8pEVsovf6fXd2gz$1WE?H7+?Oogg~)H$x*q^
zgR8$ccqmv7`L}qPQ55e-PJd8Jg)!|W+7XtrmRptTUd5RjN{3y~yTx<{B_Zj=WPrYFo%k|UAiY}t
z+_Kic+o5n1V1nmb2dU-?>u`nk71H#)^PwgK+_g!FYn6rtaB3pKPl5iLer)ee&_}WP
z)Fq(Ykhx8|#}ZsC$RRccTPJP7&uw>U1`e*8K1eM6)jHvj{Y?Lutn7sv$R8+Qn%SJk{{SBtb=eKa{HHAQSDuh}5Z1t%NyX}lJs%$ucm@SaJ9rfFz(+BKTv)HhpRPw!2pz1rim>f5XsdU
zD7>Nr{@+1<)7S%oeCKh0X;?Ku5tUu*B8u7L{-mAYi@J-iC5^7-m-O&5dG;;II!18i_MvhMpFQud;s4L|!#YWm%I9=f@A0*(ykKFTsL}HCwKc#81VCS=KIQ|7
zqbClgcFEQN+{5g9-=NT+pG9uIS0@sAORH}k#JAqxhn}U(M_C=Rg)a$(`02RL-2m2P
z9+-X<7VScD42RcSS_%sYT|XcK+pL-=51U%7yaNZ<8}2TAQfB?=-IvRGsfX6#c7IWO
z5ffzs0av~jfn_2Wy;Ix%22Ga_T$HAKw^?v{x;ZoV0oFybg^0mO_ooj-Xj|OpyXX^7@(dS_ng4oS`y|V@jNw)zP
zrzxH`LTkq53w*owABZ`$ujT@x^af<;tM*2c6&RpazJ+EM?B-PN+_Zr!xNc3y3s{Ey
z26Naap4;U*X?^#GNn