1
0
mirror of synced 2025-12-19 09:57:42 -05:00

Fix old copy syntax

This commit is contained in:
Kevin Heis
2023-09-25 11:30:36 -07:00
parent b8bd4630f6
commit 65e69af7f8
7 changed files with 9 additions and 9 deletions

View File

@@ -65,7 +65,7 @@ Edit the trust policy, adding the `sub` field to the validation conditions. For
If you use a workflow with an environment, the `sub` field must reference the environment name: `repo:OWNER/REPOSITORY:environment:NAME`. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token)." If you use a workflow with an environment, the `sub` field must reference the environment name: `repo:OWNER/REPOSITORY:environment:NAME`. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token)."
```json{:copy} ```json copy
"Condition": { "Condition": {
"StringEquals": { "StringEquals": {
"{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:aud": "sts.amazonaws.com", "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:aud": "sts.amazonaws.com",

View File

@@ -51,7 +51,7 @@ The [`pypa/gh-action-pypi-publish`](https://github.com/marketplace/actions/pypi-
The following example uses the `pypa/gh-action-pypi-publish` action to exchange an OIDC token for a PyPI API token, which is then used to upload a package's release distributions to PyPI. The following example uses the `pypa/gh-action-pypi-publish` action to exchange an OIDC token for a PyPI API token, which is then used to upload a package's release distributions to PyPI.
```yaml{:copy} ```yaml copy
jobs: jobs:
release-build: release-build:
runs-on: ubuntu-latest runs-on: ubuntu-latest

View File

@@ -116,7 +116,7 @@ To ensure users can sign into the new target instance, ensure that your environm
1. Wait for the configuration run to complete. 1. Wait for the configuration run to complete.
1. To ensure that the target instance's configuration contains the keys, run the following {% ifversion ghes = 3.7 %}command{% elsif ghes = 3.8 or ghes = 3.9 %}commands{% endif %} and verify that the output matches step 1{% ifversion ghes = 3.8 or ghes = 3.9 %} and step 4{% endif %}. 1. To ensure that the target instance's configuration contains the keys, run the following {% ifversion ghes = 3.7 %}command{% elsif ghes = 3.8 or ghes = 3.9 %}commands{% endif %} and verify that the output matches step 1{% ifversion ghes = 3.8 or ghes = 3.9 %} and step 4{% endif %}.
```shell{:copy} ```shell copy
ghe-config secrets.github.encrypted-column-keying-material ghe-config secrets.github.encrypted-column-keying-material
{%- ifversion ghes = 3.8 or ghes = 3.9 %} {%- ifversion ghes = 3.8 or ghes = 3.9 %}
ghe-config secrets.github.encrypted-column-current-encryption-key ghe-config secrets.github.encrypted-column-current-encryption-key

View File

@@ -33,7 +33,7 @@ If you enable the collection of data about {% data variables.product.prodname_ac
{% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.enterprise_installation.ssh-into-instance %}
1. Enter the following command. 1. Enter the following command.
```shell{:copy} ```shell copy
ghe-config app.github.enable-actions-usage-stats true ghe-config app.github.enable-actions-usage-stats true
``` ```

View File

@@ -31,7 +31,7 @@ You can create tasklists using Markdown in the issue description (the opening co
You can add a tasklist by copying the Markdown below into your issue description: You can add a tasklist by copying the Markdown below into your issue description:
````markdown{:copy} ````markdown copy
```[tasklist] ```[tasklist]
### My tasks ### My tasks
- [ ] https://github.com/octo-org/octo-repo/issues/45 - [ ] https://github.com/octo-org/octo-repo/issues/45

View File

@@ -100,7 +100,7 @@ You can create multiple tasklists in a single issue. Each tasklist has its own t
1. In the menu, click **Edit**. 1. In the menu, click **Edit**.
1. In the issue description, below your first tasklist, add the Markdown below: 1. In the issue description, below your first tasklist, add the Markdown below:
````markdown{:copy} ````markdown copy
```[tasklist] ```[tasklist]
### Tasks ### Tasks
- [ ] Draft task - [ ] Draft task

View File

@@ -4,7 +4,7 @@ This file tracks metadata for videos embedded in GitHub Docs.
Add the following metadata for every video added docs. Add the following metadata for every video added docs.
```markdown{:copy} ```text copy
Title: Video title Title: Video title
URL: YouTube.com/ URL: YouTube.com/
Description: One sentence Description: One sentence
@@ -15,7 +15,7 @@ Location: /where/in/docs
Transcript: ./content/video-transcripts/filename Transcript: ./content/video-transcripts/filename
``` ```
``` ```text
Title: Codespaces - Your instant dev box in the cloud Title: Codespaces - Your instant dev box in the cloud
URL: https://www.youtube-nocookie.com/embed/_W9B7qc9lVc URL: https://www.youtube-nocookie.com/embed/_W9B7qc9lVc
Description: A 1.5 minute overview of GitHub Codespaces. Description: A 1.5 minute overview of GitHub Codespaces.
@@ -26,7 +26,7 @@ Location: /content/codespaces/index.md
Transcript: /video-transcripts/transcript-codespaces-your-instant-dev-box-in-the-cloud Transcript: /video-transcripts/transcript-codespaces-your-instant-dev-box-in-the-cloud
``` ```
``` ```text
Title: Using Projects for feature planning Title: Using Projects for feature planning
URL: https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y URL: https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y
Description: Check out all the cool new things you can do with your GitHub Projects powered by GitHub Issues Description: Check out all the cool new things you can do with your GitHub Projects powered by GitHub Issues