Merge branch 'main' into scheduled-workflow-tests

Author: sarahs

.github/ISSUE_COMMENT_TEMPLATE/status.yml

@@ -1,6 +1,6 @@
 ---
 name: Status Update
-about: A brief status update.
+description: A brief status update.
 body:
   - type: dropdown
     attributes:

.github/ISSUE_COMMENT_TEMPLATE/target-date.yml

@@ -1,6 +1,6 @@
 ---
 name: Target Date Update
-about: Target date update
+description: Target date update
 body:
   - type: input
     attributes:

.github/workflows/check-for-spammy-issues.yml

@@ -65,3 +65,14 @@ jobs:
               issue_number: issue.number,
               body: "This issue appears to have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in [discussions](https://github.com/github/docs/discussions)!"
             });
+
+            // Add the issue to the Done column on the triage board
+            try {
+              await github.projects.createCard({
+                column_id: 11167427,
+                content_id: context.payload.issue.id,
+                content_type: "Issue"
+              });
+            } catch (error) {
+              console.log(error);
+            }

.github/workflows/send-prs-to-how-how-we-work-boards.yml

@@ -0,0 +1,45 @@
+name: Send pull_request to How We Work Boards
+
+# **What it does**: This sends pull requests with the feature label to the Docs Engineering feature board
+# **Why we have it**: If we use PRs to track features this automates them ending up on the feature board
+# **Who does it impact**: Docs Engineering team members
+
+on:
+  pull_request:
+    types:
+      - labeled
+      - opened
+      - reopened
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    steps:
+      - if: (github.repository == 'github/docs-internal' || github.repository == 'github/docs') && (contains(github.event.pull_request.labels.*.name, 'engineering') && contains(github.event.pull_request.labels.*.name, 'feature'))
+        uses: actions/github-script@626af12fe9a53dc2972b48385e7fe7dec79145c9
+        with:
+          github-token: ${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}
+          script: |
+            // Only do this for work by the engineering folks since multiple teams do work
+            // in the docs repos
+            try {
+              await github.teams.getMembershipForUserInOrg({
+                org: 'github',
+                team_slug: 'docs-engineering',
+                username: context.payload.sender.login,
+              });
+            } catch(err) {
+              return
+            }
+
+            var column_id = 13445681;
+            try {
+              github.projects.createCard({
+                column_id: column_id,
+                content_id: context.payload.pull_request.id,
+                content_type: "PullRequest"
+              });
+            } catch (error) {
+              console.log(error);
+            }

.pa11yci

@@ -24,7 +24,7 @@
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address",
     "http://localhost:4001/en/github/authenticating-to-github/configuring-two-factor-authentication",
     "http://localhost:4001/en/rest",
-    "http://localhost:4001/en/github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site",
+    "http://localhost:4001/en/pages/configuring-a-custom-domain-for-your-github-pages-site",
     "http://localhost:4001/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile",
@@ -36,17 +36,17 @@
     "http://localhost:4001/en/github/authenticating-to-github/testing-your-ssh-connection",
     "http://localhost:4001/en/github/getting-started-with-github/fork-a-repo",
     "http://localhost:4001/en/graphql",
-    "http://localhost:4001/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site",
+    "http://localhost:4001/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site",
     "http://localhost:4001/en/developers",
     "http://localhost:4001/en/github/getting-started-with-github/supported-browsers",
     "http://localhost:4001/en/github/managing-your-work-on-github/about-project-boards",
     "http://localhost:4001/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork",
-    "http://localhost:4001/en/github/working-with-github-pages/creating-a-github-pages-site",
+    "http://localhost:4001/en/pages/getting-started-with-github-pages/creating-a-github-pages-site",
     "http://localhost:4001/en/github/authenticating-to-github/working-with-ssh-key-passphrases",
     "http://localhost:4001/en/github/authenticating-to-github",
     "http://localhost:4001/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages",
-    "http://localhost:4001/en/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site",
-    "http://localhost:4001/en/github/working-with-github-pages/about-github-pages",
+    "http://localhost:4001/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site",
+    "http://localhost:4001/en/pages/getting-started-with-github-pages/about-github-pages",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-profile",
     "http://localhost:4001/en/actions/getting-started-with-github-actions/about-github-actions",
     "http://localhost:4001/en/github/getting-started-with-github",
@@ -75,7 +75,7 @@
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-user-account/changing-your-github-username",
     "http://localhost:4001/en/github/getting-started-with-github/create-a-repo",
-    "http://localhost:4001/en/github/working-with-github-pages/getting-started-with-github-pages",
+    "http://localhost:4001/en/pages/getting-started-with-github-pages",
     "http://localhost:4001/en/github/administering-a-repository/deleting-a-repository",
     "http://localhost:4001/en/actions/configuring-and-managing-workflows/using-environment-variables",
     "http://localhost:4001/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets",
@@ -86,7 +86,7 @@
     "http://localhost:4001/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue",
     "http://localhost:4001/en/github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates",
     "http://localhost:4001/en/github/authenticating-to-github/about-two-factor-authentication",
-    "http://localhost:4001/en/github/working-with-github-pages/about-custom-domains-and-github-pages",
+    "http://localhost:4001/en/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages",
     "http://localhost:4001/en/github/searching-for-information-on-github/searching-code",
     "http://localhost:4001/en/github/getting-started-with-github/configuring-git-to-handle-line-endings",
     "http://localhost:4001/en/github/getting-started-with-github/getting-changes-from-a-remote-repository",
@@ -95,7 +95,7 @@
     "http://localhost:4001/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository",
     "http://localhost:4001/en/github/getting-started-with-github/verifying-your-email-address",
     "http://localhost:4001/en/github/setting-up-and-managing-your-github-profile/personalizing-your-profile",
-    "http://localhost:4001/en/github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll",
+    "http://localhost:4001/en/pages/setting-up-a-github-pages-site-with-jekyll",
     "http://localhost:4001/en/github/managing-subscriptions-and-notifications-on-github",
     "http://localhost:4001/en/github/collaborating-with-issues-and-pull-requests/configuring-a-remote-for-a-fork"
   ]

assets/images/help/settings/personal_access_tokens.png

@@ -32,6 +32,7 @@ topics:
   {% link_in_list /about-using-actions-on-github-enterprise-server %}
   {% link_in_list /enabling-automatic-access-to-githubcom-actions-using-github-connect %}
   {% link_in_list /manually-syncing-actions-from-githubcom %}
+  {% link_in_list /using-the-latest-version-of-the-official-bundled-actions %}
   {% link_in_list /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access %}
 
 {% topic_link_in_list /advanced-configuration-and-troubleshooting %}

assets/images/help/settings/personal_access_tokens_ghe.png

@@ -0,0 +1,45 @@
+---
+title: Using the latest version of the official bundled actions
+intro: 'You can update the actions that are bundled with your {% data variables.product.prodname_ghe_server %} instance, or use actions directly from {% data variables.product.prodname_dotcom_the_website %}.'
+versions:
+  enterprise-server: '>=2.22'
+topics:
+  - enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+Your {% data variables.product.prodname_ghe_server %} instance includes a number of built-in actions that you can use in your workflows. For more information about the bundled actions, see ["Official actions bundled with {% data variables.product.prodname_ghe_server %}"](/admin/github-actions/about-using-actions-on-github-enterprise-server#official-actions-bundled-with-github-enterprise-server).
+
+These bundled actions are a point-in-time snapshot of the official actions found at https://github.com/actions; as a result, these actions may be older versions that can be updated. To update these actions, you can use `actions-sync` to retrieve updated versions from {% data variables.product.prodname_dotcom_the_website %}.
+
+Alternatively, if your {% data variables.product.prodname_ghe_server %} instance has {% data variables.product.prodname_github_connect %} enabled, then you have additional options for using the latest actions from {% data variables.product.prodname_dotcom_the_website %}:
+
+- Your workflow file can directly reference a specific tag that only exists on {% data variables.product.prodname_dotcom_the_website %}.
+- To force the workflow file to use the actions on {% data variables.product.prodname_dotcom_the_website %}, you can edit the tag assigned to the bundled actions.
+
+These options are described in more detail in the following sections.
+
+### Using actions-sync to update a bundled action
+
+To update the bundled actions, you can use the `actions-sync` tool to synchronize actions with {% data variables.product.prodname_dotcom_the_website %}. For more information on using `actions-sync`, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom)."
+
+### Using actions from {% data variables.product.prodname_dotcom_the_website %}
+
+{% data reusables.github-actions.actions-github-connect-requirement %}
+
+Once configured, you can use a new version of an action from {% data variables.product.prodname_dotcom_the_website %} by manually specifying the required version in the workflow file. For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}, you can specify the tag `actions/setup-python@v2.2.1` in your workflow file.
+
+### Using the latest version by removing the specific action's tag
+
+{% data reusables.github-actions.actions-github-connect-requirement %}
+
+If you remove the version tag that was previously assigned to an action, {% data variables.product.prodname_ghe_server %} will check {% data variables.product.prodname_dotcom_the_website %} for the required tag. For more information on working with tags, see "[Viewing tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags#viewing-tags)."
+
+For example, to use version `v2.2.1` of `actions/setup-python` from {% data variables.product.prodname_dotcom_the_website %}:
+
+1. In {% data variables.product.prodname_ghe_server %}, delete the `v2` tag from the `actions/setup-python` repository.
+1. Create a workflow that uses `actions/setup-python` with the `v2` tag.
+
+When the workflow is unable to find the specified `v2` tag on {% data variables.product.prodname_ghe_server %}, it checks {% data variables.product.prodname_dotcom_the_website %} for the required tag. If it finds a tagged version of that action, {% data variables.product.prodname_ghe_server %} uses the version from {% data variables.product.prodname_dotcom_the_website %}.