Branch was updated using the 'autoupdate branch' Actions workflow.

Author: Octomerger

.github/ISSUE_COMMENT_TEMPLATE/status.yml …/ISSUE_COMMENT_TEMPLATE/quick-status.yml.github/ISSUE_COMMENT_TEMPLATE/status.yml renamed to .github/ISSUE_COMMENT_TEMPLATE/quick-status.yml .github/ISSUE_COMMENT_TEMPLATE/status.yml renamed to .github/ISSUE_COMMENT_TEMPLATE/quick-status.yml

@@ -1,26 +1,25 @@
 ---
-name: Status Update
-about: A brief status update.
+name: A Brief status Update
+description: A brief status update.
 body:
   - type: dropdown
     attributes:
-      name: Status
+      label: Status
       options:
-        - name: "GREEN \U0001F34F (All good, smooth sailing)"
+        - label: "GREEN \U0001F34F (All good, smooth sailing)"
           value: 'Status: GREEN'
-        - name: "YELLOW \U0001F7E1 (On track, with hurdles to work through)"
+        - label: "YELLOW \U0001F7E1 (On track, with hurdles to work through)"
           value: 'Status: YELLOW'
-        - name: "RED \U0001F534 (BLOCKED)"
+        - label: "RED \U0001F534 (BLOCKED)"
           value: 'Status: RED'
-  - type: input
+  - type: textarea
     attributes:
-      name: Update Summary
+      label: Update Summary
       placeholder:
         Brief summary of the status and next steps. Any blockers should be
         called out specifically.
-      inputType: longText
   - type: input
     attributes:
-      name: 'Attribution'
+      label: 'Attribution'
       value: '_created with :heart: by typing_ `/status`'
-      inputType: text
+      format: text

.github/ISSUE_COMMENT_TEMPLATE/target-date.yml

@@ -20,7 +20,7 @@ jobs:
           stale-pr-message: 'This PR is stale because it has been open 60 days with no activity.'
           days-before-stale: 60
           days-before-close: -1
-          only-labels: 'engineering'
+          only-labels: 'engineering,Triaged,Improve existing docs,Core,Ecosystem'
           stale-issue-label: 'stale'
           stale-pr-label: 'stale'
           exempt-pr-labels: 'never-stale'

.github/workflows/60-days-stale-check.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/check-for-spammy-issues.yml

@@ -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"
   ]

.pa11yci

@@ -48,7 +48,7 @@ With auto-merge, pull requests can be set to merge automatically when all merge
 #### Developer changes
 
 - [Organization owners can now disable publication](/github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization) of {% data variables.product.prodname_pages %} sites from repositories in the organization. This will not unpublish existing sites.
-- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).
+- Repositories that use {% data variables.product.prodname_pages %} can now [build and deploy from any branch](/pages/getting-started-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites).
 - When writing an issue or pull request, the list syntax for bullets, numbers, and tasks will now be autocompleted after you press `return` or `enter`.
 - You can now delete a directory in a repository from the repository page. When navigating to a directory, a new kebab button next to the "Add file" button gives the option to delete the directory.
 - It’s now easier and faster to [reference issues or pull requests](/github/writing-on-github/basic-writing-and-formatting-syntax#referencing-issues-and-pull-requests), with search across multiple words after the "#".  

content/admin/overview/github-ae-release-notes.md

@@ -94,4 +94,4 @@ Your language and server implementations may differ from this example code. Howe
 
 * Using a plain `==` operator is **not advised**. A method like [`secure_compare`][secure_compare] performs a "constant time" string comparison, which helps mitigate certain timing attacks against regular equality operators.
 
-[secure_compare]: http://rubydoc.info/github/rack/rack/master/Rack/Utils.secure_compare
+[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare

content/developers/webhooks-and-events/securing-your-webhooks.md

@@ -11,7 +11,11 @@ topics:
   - repositories
 ---
 
-If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+### About auto-merge
+
+If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
+
+### Managing auto-merge
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}

content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md

@@ -17,7 +17,7 @@ When you rename a repository, all existing information, with the exception of pr
 * Stars
 * Followers
 
-For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
 
 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:
 
@@ -29,7 +29,7 @@ For more information, see "[Managing remote repositories](/github/getting-starte
 
 {% if currentVersion == "free-pro-team@latest" %}
 
-If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/about-custom-domains-and-github-pages)." 
+If you plan to rename a repository that has a {% data variables.product.prodname_pages %} site, we recommend using a custom domain for your site. This ensures that the site's URL isn't impacted by renaming the repository. For more information, see "[About custom domains and {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages)." 
 
 {% endif %}
 

content/github/administering-a-repository/renaming-a-repository.md

@@ -14,7 +14,9 @@ topics:
 
 If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
 
-Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."
+Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
+
+After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %}
 
 You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).