jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Removes em/span tags according to docs-team 3076 (#40098)

Browse Source
This commit is contained in:
Ben Ahmady
2023-08-09 09:37:22 +01:00
committed by GitHub
parent ea3bcbd451
commit 3db20c8b9c
12 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -85,7 +85,7 @@ You can use the `git config` command to change the email address you associate w
```shell
$ git config --global user.email
<span class="output">email@example.com</span>
email@example.com
```
1. {% data reusables.user-settings.link_email_with_your_account %}
@@ -109,7 +109,7 @@ You can change the email address associated with commits you make in a single re
```shell
$ git config user.email
<span class="output">email@example.com</span>
email@example.com
```
1. {% data reusables.user-settings.link_email_with_your_account %}

2
content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md
View File

@@ -115,5 +115,5 @@ To use a different SSH key for different repositories that you clone to your wor
For example, the following command sets the `GIT_SSH_COMMAND` environment variable to specify an SSH command that uses the private key file at **_PATH/TO/KEY/FILE_** for authentication to clone the repository named OWNER/REPOSITORY on {% data variables.location.product_location %}.
<pre>
GIT_SSH_COMMAND='ssh -i <em>PATH/TO/KEY/FILE</em> -o IdentitiesOnly=yes' git clone git@github.com:<em>OWNER</em>/<em>REPOSITORY</em>
GIT_SSH_COMMAND='ssh -i PATH/TO/KEY/FILE -o IdentitiesOnly=yes' git clone git@github.com:OWNER/REPOSITORY
</pre>

2
content/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance.md
View File

@@ -261,7 +261,7 @@ $ ghe-restore -c 169.154.1.1
> WARNING: All data on GitHub Enterprise appliance 169.154.1.1 (v2.9.0)
> will be overwritten with data from snapshot 20170329T150710.
> Please verify that this is the correct restore host before continuing.
> Type 'yes' to continue: <em>yes</em>
> Type 'yes' to continue: yes
> Starting restore of 169.154.1.1:122 from snapshot 20170329T150710
# ...output truncated

2
content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md
View File

@@ -43,7 +43,7 @@ To more accurately mirror your production environment, you can optionally copy f
- For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). For example:
```shell
azcopy copy 'https://<em>SOURCE-STORAGE-ACCOUNT-NAME</em>.blob.core.windows.net/<em>SAS-TOKEN</em>' 'https://<em>DESTINATION-STORAGE-ACCOUNT-NAME</em>.blob.core.windows.net/' --recursive
azcopy copy 'https://SOURCE-STORAGE-ACCOUNT-NAME.blob.core.windows.net/SAS-TOKEN' 'https://DESTINATION-STORAGE-ACCOUNT-NAME.blob.core.windows.net/' --recursive
```
- For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). For example:

2
content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
View File

@@ -92,7 +92,7 @@ Ensure that you configure signed assertions for the {% data variables.product.pr
If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log.
```
Audience is invalid. Audience attribute does not match https://<em>YOUR-INSTANCE-URL</em>
Audience is invalid. Audience attribute does not match https://YOUR-INSTANCE-URL
```
Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {% data variables.location.product_location %}, which is the full URL to your instance. For example, `https://ghe.corp.example.com`.

2
content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
View File

@@ -94,7 +94,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
```shell
$ ssh-add -l -E sha256
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
> 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
```
{% endlinux %}

2
content/get-started/using-git/dealing-with-non-fast-forward-errors.md
View File

@@ -19,7 +19,7 @@ If another person has pushed to the same branch as you, Git won't be able to pus
$ git push origin main
> 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 %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git'
> 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
> Merge the remote changes (e.g. 'git pull') before pushing again. See the
> 'Note about fast-forwards' section of 'git push --help' for details.

14
content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
View File

@@ -782,8 +782,8 @@ You can find the node ID of a {% data variables.product.product_name %} user or
```shell
curl --request GET \
--url https://api.github.com/users/<em>GITHUB_OWNER</em> \
--header 'Authorization: token <em>TOKEN</em>' \
--url https://api.github.com/users/GITHUB_OWNER \
--header 'Authorization: token TOKEN' \
--header 'Accept: application/vnd.github+json'
```
@@ -792,7 +792,7 @@ curl --request GET \
{% cli %}
```shell
gh api -H "Accept: application/vnd.github+json" /users/<em>GITHUB_OWNER</em>
gh api -H "Accept: application/vnd.github+json" /users/GITHUB_OWNER
```
{% endcli %}
@@ -804,8 +804,8 @@ To create the project, replace `OWNER_ID` with the node ID of the new project ow
```shell
curl --request POST \
--url https://api.github.com/graphql \
--header 'Authorization: token <em>TOKEN</em>' \
--data '{"query":"mutation {createProjectV2(input: {ownerId: \"<em>OWNER_ID</em>\" title: \"<em>PROJECT_NAME</em>\"}) {projectV2 {id}}}"}'
--header 'Authorization: token TOKEN' \
--data '{"query":"mutation {createProjectV2(input: {ownerId: \"OWNER_ID\" title: \"PROJECT_NAME\"}) {projectV2 {id}}}"}'
```
{% endcurl %}
@@ -817,8 +817,8 @@ gh api graphql -f query='
mutation{
createProjectV2(
input: {
ownerId: "<em>OWNER_ID</em>",
title: "<em>PROJECT_NAME</em>"
ownerId: "OWNER_ID",
title: "PROJECT_NAME"
}
){
projectV2 {

2
content/packages/quickstart.md
View File

@@ -95,7 +95,7 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
- Edit the `package.json` file and specify the `publishConfig` key:
```shell
"publishConfig": {
"@<em>YOUR-USERNAME</em>:registry": "https://npm.pkg.github.com"
"@YOUR-USERNAME:registry": "https://npm.pkg.github.com"
}
```
1. Commit and push your changes to {% data variables.product.prodname_dotcom %}.

10
content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
View File

@@ -54,7 +54,7 @@ To keep your credentials secure, we recommend you save your {% data variables.pr
{% raw %}
```shell
cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u USERNAME --password-stdin
```
{% endraw %}
@@ -209,7 +209,7 @@ $ docker images
> REPOSITORY TAG IMAGE ID CREATED SIZE
> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB
# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
# Tag the image with OWNER/REPO/IMAGE_NAME
$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
# Push the image to {% data variables.product.prodname_registry %}
@@ -224,7 +224,7 @@ $ docker images
> REPOSITORY TAG IMAGE ID CREATED SIZE
> monalisa 1.0 c75bebcdd211 4 weeks ago 1.11MB
# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
# Tag the image with OWNER/REPO/IMAGE_NAME
$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0
# Push the image to {% data variables.product.prodname_registry %}
@@ -238,7 +238,7 @@ You can publish a new Docker image for the first time and name it `monalisa`.
{% ifversion fpt or ghec %}
```shell
# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
# Build the image with docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
# Assumes Dockerfile resides in the current working directory (.)
$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
@@ -249,7 +249,7 @@ $ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
{% else %}
```shell
# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
# 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 .

2
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
View File

@@ -88,7 +88,7 @@ Only the user who created the pull request can give you permission to push commi
1. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`:
```shell
$ git push origin <em>test-branch</em>
$ git push origin test-branch
> Counting objects: 32, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (26/26), done.

4
content/repositories/working-with-files/using-files/working-with-non-code-files.md
View File

@@ -256,7 +256,7 @@ See [version 1.1.0 of the open simplestyle spec](https://github.com/mapbox/simpl
### Embedding your map elsewhere
Want to make your GeoJSON map available someplace other than {% data variables.product.product_name %}? Simply modify this template, and place it in any HTML page that supports JavaScript (e.g., [{% data variables.product.prodname_pages %}](https://pages.github.com)):
Want to make your GeoJSON map available someplace other than {% data variables.product.product_name %}? Simply modify this template, and place it in any HTML page that supports JavaScript (for example, [{% data variables.product.prodname_pages %}](https://pages.github.com)):
```html
<script src="https://embed.github.com/view/geojson/<username>/<repo>/<ref>/<path_to_file>"></script>
@@ -295,7 +295,7 @@ The underlying map data (street names, roads, etc.) are driven by [OpenStreetMap
### Troubleshooting GeoJSON/TopoJSON files
If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). If your points aren't appearing where you'd expect (<em>e.g.</em>, in the middle of the ocean), it's likely that the data is in a projection which is currently unsupported. Currently, {% data variables.product.product_name %} only supports the `urn:ogc:def:crs:OGC:1.3:CRS84` projection.
If you're having trouble rendering GeoJSON files, ensure you have a valid GeoJSON file by running it through a [GeoJSON linter](http://geojsonlint.com/). If your points aren't appearing where you'd expect (for example, in the middle of the ocean), it's likely that the data is in a projection which is currently unsupported. Currently, {% data variables.product.product_name %} only supports the `urn:ogc:def:crs:OGC:1.3:CRS84` projection.
Additionally, if your `.geojson` file is especially large (over 10 MB), it is not possible to render within the browser. If that's the case, you'll generally see a message that says we can't show files that large.