Merge pull request #44344 from github/repo-sync

Repo sync

Author: docs-bot

CHANGELOG.md

@@ -6,6 +6,14 @@ We published the first iteration of a [journey landing page](https://docs.github
 
 <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:

content/account-and-profile/how-tos/account-management/moving-your-work-to-an-organization.md

@@ -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)

content/actions/how-tos/troubleshoot-workflows.md

@@ -142,6 +142,14 @@ If you use self-hosted runners, you can view their activity and diagnose common
 
 For more information, see [AUTOTITLE](/actions/how-tos/manage-runners/self-hosted-runners/monitor-and-troubleshoot).
 
+{% ifversion fpt or ghec %}
+
+### Runner IP addresses flagged by security scanners
+
+{% data reusables.actions.runner-ip-reputation %}
+
+{% endif %}
+
 ## Networking troubleshooting suggestions
 
 Our support is limited for network issues that involve:

content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md

@@ -31,6 +31,12 @@ We make changes to our IP addresses from time to time. We do not recommend allow
 
 For applications to function, you must allow TCP ports 22, 80, and 443 via our IP ranges for `github.com` and `{% data variables.enterprise.data_residency_domain %}`.
 
+## {% data variables.product.prodname_actions %} runner IP addresses and third-party IP reputation services
+
+{% data reusables.actions.runner-ip-reputation %}
+
+For more information about {% data variables.product.prodname_actions %} runner IP ranges, see [AUTOTITLE](/actions/how-tos/troubleshoot-workflows#runner-ip-addresses-flagged-by-security-scanners).
+
 ## Further reading
 
 * [AUTOTITLE](/get-started/using-github/troubleshooting-connectivity-problems)

content/code-security/reference/security-incident-response/investigation-areas.md

@@ -128,6 +128,12 @@ You found suspicious code in your repository, a security researcher reported an
 
 * [Containment actions](/code-security/tutorials/secure-your-organization/responding-to-security-incidents#step-2-contain-the-threat)
 
+{% ifversion fpt or ghec %}
+
+{% data reusables.actions.runner-ip-reputation-note %}
+
+{% endif %}
+
 ## Malware and supply chain attacks
 
 This section may apply when:

content/code-security/tutorials/secure-your-organization/responding-to-security-incidents.md

@@ -47,6 +47,12 @@ Try to identify the nature of the signal you're seeing. For example, does the si
 
 For help identifying these threat signals across your organization or enterprise, consult [AUTOTITLE](/code-security/reference/security-incident-response/investigation-areas).
 
+{% ifversion fpt or ghec %}
+
+{% data reusables.actions.runner-ip-reputation-note %}
+
+{% endif %}
+
 We suggest you don't spend too much time on deep inspection in the earlier stages of your investigation, since the initial goal is to **identify** the threat signal in order to **validate** it and strategize your response.
 
 ### 2. Validate