Merge branch 'main' into registry-specific-path

Author: lecoursen

.github/allowed-actions.js

@@ -24,7 +24,7 @@ module.exports = [
   'lee-dohm/close-matching-issues@22002609b2555fe18f52b8e2e7c07cbf5529e8a8',
   'pascalgn/automerge-action@c9bd182',
   'peter-evans/create-issue-from-file@a04ce672e3acedb1f8e416b46716ddfd09905326',
-  'peter-evans/create-or-update-project-card@80140aaeb9730972a83c626031250621fe8f6670',
+  'peter-evans/create-or-update-comment@5221bf4aa615e5c6e95bb142f9673a9c791be2cd',
   'peter-evans/create-pull-request@938e6aea6f8dbdaced2064e948cb806c77fe87b8',
   'rachmari/actions-add-new-issue-to-column@1a459ef92308ba7c9c9dc2fcdd72f232495574a9',
   'rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e',

.github/workflows/check-all-english-links.yml

@@ -19,7 +19,6 @@ jobs:
       - name: Run script
         run: |
           script/check-english-links.js > broken_links.md
-          echo -e '\ncc @github/docs-content'>> broken_links.md
       - if: ${{ failure() }}
         name: Get title for issue
         id: check
@@ -28,7 +27,7 @@ jobs:
         name: Close previous report
         uses: lee-dohm/close-matching-issues@22002609b2555fe18f52b8e2e7c07cbf5529e8a8
         with:
-          query: 'label:"broken+link+report"'
+          query: 'label:"broken link report"'
           token: ${{ secrets.DOCUBOT_FR_PROJECT_BOARD_WORKFLOWS_REPO_ORG_READ_SCOPES }}
       - if: ${{ failure() }}
         name: Create issue from file
@@ -40,11 +39,10 @@ jobs:
           content-filepath: ./broken_links.md
           labels: broken link report
       - if: ${{ failure() }}
-        name: Add issue to FR project board
-        uses: peter-evans/create-or-update-project-card@80140aaeb9730972a83c626031250621fe8f6670
+        name: Add comment to issue
+        uses: peter-evans/create-or-update-comment@5221bf4aa615e5c6e95bb142f9673a9c791be2cd
         with:
-          project-repository: 'github'
-          project-number: '1367'
-          column-name: 'Docs-content FR issues'
+          body: |
+            cc @github/docs-content
           issue-number: ${{ steps.broken-link-report.outputs.issue-number }}
           token: ${{ secrets.DOCUBOT_FR_PROJECT_BOARD_WORKFLOWS_REPO_ORG_READ_SCOPES }}

.github/workflows/openapi-decorate.yml

@@ -10,6 +10,11 @@ jobs:
     if: github.event.pull_request.user.login == 'github-openapi-bot'
     runs-on: ubuntu-latest
     steps:
+      - name: Label pull requests with 'github-openapi-bot'
+        uses: rachmari/labeler@832d42ec5523f3c6d46e8168de71cd54363e3e2e
+        with:
+          repo-token: '${{ secrets.GITHUB_TOKEN }}'
+          add-labels: 'github-openapi-bot'
       - name: Checkout repository code
         uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
 

.github/workflows/test.yml

@@ -36,7 +36,8 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        test-group: [content, meta, rendering, routing, unit, links-and-images]
+        test-group:
+          [content, meta, rendering, routing, unit, links-and-images, graphql]
     steps:
       # Each of these ifs needs to be repeated at each step to make sure the required check still runs
       # Even if if doesn't do anything

.github/workflows/update-graphql-files.yml

@@ -37,20 +37,15 @@ jobs:
         env:
           # need to use a token from a user with access to github/github for this step
           GITHUB_TOKEN: ${{ secrets.ZEKE_PAT_WITH_REPO_AND_WORKFLOW_SCOPE_FOR_REPO_SYNC }}
-        # technically the changelog should only be updated once per day, but we can safely
-        # run build-changelog-from-markdown.js in its current form once per hour; when we
-        # rewrite the changelog script, we may need to run it in a separate workflow on a
-        # once-per-day schedule; see details in https://github.com/github/docs-internal/issues/12722.
         run: |
           script/graphql/update-files.js
-          script/graphql/build-changelog-from-markdown.js
       - name: Create pull request
         id: create-pull-request
         uses: peter-evans/create-pull-request@938e6aea6f8dbdaced2064e948cb806c77fe87b8
         with:
           # need to use a token with repo and workflow scopes for this step
           token: ${{ secrets.OCTOMERGER_PAT_WITH_REPO_AND_WORKFLOW_SCOPE }}
-          commit-message: 'Action ran graphql scripts "update-files" and "build-changelog-from-markdown"'
+          commit-message: 'Action ran graphql script"update-files"'
           title: GraphQL schema update
           body:
             "Hello! Some GraphQL data in github/github was updated recently. This PR

assets/images/help/organizations/repositories-dialog.png

@@ -32,8 +32,8 @@ You can build Docker container and JavaScript actions. Actions require a metadat
 | Type | Operating system |
 | ---- | ------------------- |
 | Docker container | Linux |
-| JavaScript | Linux, MacOS, Windows |
-| Composite run steps | Linux, MacOS, Windows |
+| JavaScript | Linux, macOS, Windows |
+| Composite run steps | Linux, macOS, Windows |
 
 #### Docker container actions
 

assets/images/help/organizations/repository-access-cog-button.png

@@ -22,19 +22,19 @@ Docker and JavaScript actions require a metadata file. The metadata filename mus
 
 Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
 
-### **`name`**
+### `name`
 
 **Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job.
 
-### **`author`**
+### `author`
 
 **Optional** The name of the action's author.
 
-### **`description`**
+### `description`
 
 **Required** A short description of the action.
 
-### **`inputs`**
+### `inputs`
 
 **Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
 
@@ -57,23 +57,23 @@ When you specify an input to an action in a workflow file or use a default input
 
 For example, if a workflow defined the numOctocats and octocatEyeColor inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables.
 
-#### **`inputs.<input_id>`**
+#### `inputs.<input_id>`
 
 **Required** A `string` identifier to associate with the input. The value of `<input_id>` is a map of the input's metadata. The `<input_id>` must be a unique identifier within the `inputs` object. The `<input_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
 
-#### **`inputs.<input_id>.description`**
+#### `inputs.<input_id>.description`
 
 **Required** A `string` description of the input parameter.
 
-#### **`inputs.<input_id>.required`**
+#### `inputs.<input_id>.required`
 
 **Required** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required.
 
-#### **`inputs.<input_id>.default`**
+#### `inputs.<input_id>.default`
 
 **Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file.
 
-### **`outputs`**
+### `outputs`
 
 **Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions.  For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.
 
@@ -87,15 +87,15 @@ outputs:
     description: 'The sum of the inputs'
 ```
 
-#### **`outputs.<output_id>`**
+#### `outputs.<output_id>`
 
 **Required** A `string` identifier to associate with the output. The value of `<output_id>` is a map of the output's metadata. The `<output_id>` must be a unique identifier within the `outputs` object. The `<output_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
 
-#### **`outputs.<output_id>.description`**
+#### `outputs.<output_id>.description`
 
 **Required** A `string` description of the output parameter.
 
-### **`outputs`** for composite run steps actions
+### `outputs` for composite run steps actions
 
 **Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#outputs)"), but also includes the `value` token.
 
@@ -116,12 +116,12 @@ runs:
 ```
 {% endraw %}
 
-#### **`outputs.<output_id.value>`**
+#### `outputs.<output_id>.value`
 **Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step.
 
 For more information on how to use context and expression syntax, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
-### **`runs`** for JavaScript actions
+### `runs` for JavaScript actions
 
 **Required** Configures the path to the action's code and the application used to execute the code.
 
@@ -133,15 +133,15 @@ runs:
   main: 'main.js'
 ```
 
-#### **`runs.using`**
+#### `runs.using`
 
 **Required** The application used to execute the code specified in [`main`](#runsmain).
 
-#### **`runs.main`**
+#### `runs.main`
 
 **Required** The file that contains your action code. The application specified in [`using`](#runsusing) executes this file.
 
-#### **`pre`**
+#### `pre`
 
 **Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The application specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`pre-if`](#pre-if).
 
@@ -155,7 +155,7 @@ runs:
   post: 'cleanup.js'
 ```
 
-#### **`pre-if`**
+#### `pre-if`
 
 **Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`.
 Note that the `step` context is unavailable, as no steps have run yet. 
@@ -167,7 +167,7 @@ In this example, `cleanup.js` only runs on Linux-based runners:
   pre-if: 'runner.os == linux'
 ```
 
-#### **`post`**
+#### `post`
 
 **Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The application specified with the [`using`](#runsusing) syntax will execute this file.
 
@@ -182,7 +182,7 @@ runs:
 
 The `post:` action always runs by default but you can override this using `post-if`.
 
-#### **`post-if`**
+#### `post-if`
 
 **Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`.
 
@@ -193,19 +193,19 @@ For example, this `cleanup.js` will only run on Linux-based runners:
   post-if: 'runner.os == linux'
 ```
 
-### **`runs`** for composite run steps actions
+### `runs` for composite run steps actions
 
 **Required** Configures the path to the composite action, and the application used to execute the code.
 
-#### **`runs.using`**
+#### `runs.using`
 
 **Required** To use a composite run steps action, set this to `"composite"`.
 
-#### **`runs.steps`**
+#### `runs.steps`
 
 **Required** The run steps that you plan to run in this action.
 
-##### **`runs.steps.run`**
+##### `runs.steps.run`
 
 **Required** The command you want to run. This can be inline or a script in your action repository:
 ```yaml
@@ -228,27 +228,27 @@ runs:
 
 For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
 
-##### **`runs.steps.shell`**
+##### `runs.steps.shell`
 
 **Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell).
 
-##### **`runs.steps.name`**
+##### `runs.steps.name`
 
 **Optional** The name of the composite run step.
 
-##### **`runs.steps.id`**
+##### `runs.steps.id`
 
 **Optional** A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Context and expression syntax for {% data variables.product.prodname_actions %}](/actions/reference/context-and-expression-syntax-for-github-actions)".
 
-##### **`runs.steps.env`**
+##### `runs.steps.env`
 
 **Optional**  Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "[email protected]" %}`echo "{name}={value}" >> $GITHUB_ENV`{% else %}`echo "::set-env name={name}::{value}"`{% endif %} in a composite run step.
 
-##### **`runs.steps.working-directory`**
+##### `runs.steps.working-directory`
 
 **Optional**  Specifies the working directory where the command is run.
 
-### **`runs`** for Docker actions
+### `runs` for Docker actions
 
 **Required** Configures the image used for the Docker action. 
 
@@ -268,11 +268,11 @@ runs:
   image: 'docker://debian:stretch-slim'
 ```
 
-#### **`runs.using`**
+#### `runs.using`
 
 **Required** You must set this value to `'docker'`.
 
-#### **`pre-entrypoint`**
+#### `pre-entrypoint`
 
 **Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`pre-if`](#pre-if).
 
@@ -290,21 +290,21 @@ runs:
   entrypoint: 'main.sh'
 ```
 
-#### **`runs.image`**
+#### `runs.image`
 
 **Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. To reference a `Dockerfile` local to your repository, use a path relative to your action metadata file. The `docker` application will execute this file.
 
-#### **`runs.env`**
+#### `runs.env`
 
 **Optional** Specifies a key/value map of environment variables to set in the container environment.
 
-#### **`runs.entrypoint`**
+#### `runs.entrypoint`
 
 **Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction.
 
 For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)."
 
-#### **`post-entrypoint`**
+#### `post-entrypoint`
 
 **Optional**  Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because  {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`post-if`](#post-if).
 
@@ -318,7 +318,7 @@ runs:
   post-entrypoint: 'cleanup.sh'
 ```
 
-#### **`runs.args`**
+#### `runs.args`
 
 **Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up.
 
@@ -344,7 +344,7 @@ runs:
 ```
 {% endraw %}
 
-### **`branding`**
+### `branding`
 
 You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
 
@@ -356,11 +356,11 @@ branding:
   color: 'green'
 ```
 
-#### **`branding.color`**
+#### `branding.color`
 
 The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`.
 
-#### **`branding.icon`**
+#### `branding.icon`
 
 The name of the [Feather](https://feathericons.com/) icon to use.
 

content/actions/creating-actions/about-actions.md

@@ -8,8 +8,6 @@ redirect_from:
 versions:
   free-pro-team: '*'
   enterprise-server: '>=2.22'
-authors:
-  - GitHub
 ---
 
 {% data reusables.actions.enterprise-beta %}

content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -11,8 +11,6 @@ redirect_from:
 versions:
   free-pro-team: '*'
   enterprise-server: '>=2.22'
-authors:
-  - GitHub
 ---
 
 {% data reusables.actions.enterprise-beta %}

content/actions/guides/publishing-nodejs-packages.md

@@ -87,7 +87,7 @@ The following operating systems are supported for the self-hosted runner applica
 - Windows Server 2016 64-bit
 - Windows Server 2019 64-bit
 
-#### MacOS
+#### macOS
 
 - macOS 10.13 (High Sierra) or later
 

content/actions/guides/setting-up-continuous-integration-using-workflow-templates.md

@@ -103,7 +103,7 @@ Printing "Hello, World!" is a great way to explore the basic set up and syntax o
     # When the event is triggered, GitHub Actions will run the jobs indicated
     jobs:
       say_hello:
-        # Uses a ubuntu-lates runner to complete the requested steps
+        # Uses a ubuntu-latest runner to complete the requested steps
         runs-on: ubuntu-latest
         steps:
         - run: |