Merge branch 'main' into patch-9

Author: Sharra-writes

.github/workflows/site-policy-reminder.yml

@@ -20,9 +20,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9
-        env:
-          GITHUB_TOKEN: ${{ secrets.API_TOKEN_SITEPOLICY }}
         with:
+          token: ${{ secrets.DOCS_BOT_PAT_BASE }}
           issue-number: ${{ github.event.pull_request.number }}
           body: |
             Before merging, please remember to change the title of this PR to a description of its changes that is suitable for public viewing on github/site-policy.

.github/workflows/site-policy-sync.yml

@@ -33,7 +33,7 @@ jobs:
         uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
         with:
           repository: github/site-policy
-          token: ${{ secrets.API_TOKEN_SITEPOLICY }}
+          token: ${{ secrets.DOCS_BOT_PAT_BASE }}
           fetch-depth: ''
           path: public-repo
 

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Docs changelog
 
+**19 May 2026**
+
+We published the first iteration of a [journey landing page](https://docs.github.com/en/enterprise-cloud@latest/copilot/get-started/enterprise-ai-governance) for enterprises adopting and governing GitHub Copilot. The journey covers sign-off and adoption, governance of core features, and agent adoption. It includes six newly published guides alongside some refreshed existing content.
+
+<hr>
+
+**16 May 2026**
+
+To help admins understand security configuration statuses, we documented the relationship between organization and enterprise configurations and repositories, including how and why that relationship changes.
+
+- [Security configuration statuses](https://docs.github.com/en/code-security/reference/security-at-scale/security-configuration-statuses) covers all 8 statuses a security configuration can have, with descriptions, causes, and recommended actions
+- [Diagnosing security configuration issues](https://docs.github.com/en/code-security/reference/security-at-scale/troubleshoot-security-configurations/diagnosing-security-configuration-issues) now covers `removed` and `removed_by_enterprise` statuses in addition to `failed`
+- [About enabling security features at scale](https://docs.github.com/en/code-security/concepts/security-at-scale/about-enabling-security-features-at-scale) explains how configurations relate to repositories over time
+
+<hr>
+
+**15 May 2026**
+
+We've published a new [GitHub Secret Protection adoption journey landing page](https://docs.github.com/en/code-security/tutorials/secret-protection-adoption-path) for AppSec administrators. Our content audit found that while individual GHSP articles existed, there was no clear end-to-end path from evaluation to organization-wide rollout. 
+
+The new page organizes existing content into a 5-phase adoption journey: assess secret risk, evaluate fit and cost, pilot with selected repositories, monitor metrics, and scale protection across your organization 🎉 
+
+<hr>
+
 **12 May 2026**
 
 We have now published the GitHub Enterprise Server (GHES) 3.21 release candidate notes. You can read the full notes here:

assets/images/help/copilot/copilot-sdk/agent-loop-architecture.png

@@ -28,5 +28,9 @@ If you want your new organization to use your current personal account username,
 
 ## Further reading
 
+{% ifversion fpt or ghec %}
 - [AUTOTITLE](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)
+{% else %}
+- [AUTOTITLE](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)
+{% endif %}
 - [AUTOTITLE](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization)

assets/images/help/copilot/copilot-sdk/agent-loop-event-flow.png

@@ -29,6 +29,11 @@ The token is also available in the `github.token` context. For more information,
 
 {% data reusables.actions.actions-do-not-trigger-workflows %}
 
+{% ifversion actions-github-token-pull-request-approval %}
+> [!NOTE]
+> If you need workflow runs from workflow-created pull requests to execute without requiring approval, use a {% data variables.product.prodname_github_app %} installation access token or a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` when creating or updating the pull request.
+{% endif %}
+
 {% data reusables.actions.actions-do-not-trigger-pages-rebuilds %}
 
 ## Next steps