Repo sync

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md

@@ -57,7 +57,8 @@ Enterprise owners can prevent {% data variables.product.pat_v1_plural %} from ac
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 1. Under {% octicon "law" aria-hidden="true" %} **Policies**, click **{% data variables.product.pat_generic_caps_plural %}**.
-1. Under **Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations**, select the option that meets your needs:
+{% ifversion tabbed-pat-settings-ui %} 1. Select the **Tokens (classic)** tab to access the {% data variables.product.pat_v1_plural %} settings.
+{% endif %}1. Under **Restrict {% data variables.product.pat_v1_plural %} from accessing your organizations**, select the option that meets your needs:
    * **Allow organizations to configure {% data variables.product.pat_v1_plural %} access requirements**: Each organization owned by the enterprise can decide whether to restrict access by {% data variables.product.pat_v1_plural %}.
    * **Restrict access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} cannot access the enterprise or organizations owned by the enterprise. SSH keys created by {% data variables.product.pat_v1_plural %} will continue to work. Organizations cannot override this setting.
    * **Allow access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} can access the enterprise and organizations owned by the enterprise. Organizations cannot override this setting.

content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md

@@ -51,7 +51,8 @@ Organization owners can prevent {% data variables.product.pat_v1_plural %} from
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 1. In the left sidebar, under **{% octicon "key" aria-hidden="true" %} {% data variables.product.pat_generic_caps %}s**, click **Settings**.
-1. Under **{% data variables.product.pat_v1_caps %}**, select the option that meets your needs:
+{% ifversion tabbed-pat-settings-ui %} 1. Select the **Tokens (classic)** tab to access the {% data variables.product.pat_v1_plural %} settings.
+{% endif %}1. Under **{% data variables.product.pat_v1_caps %}**, select the option that meets your needs:
    * **Allow access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} can access resources owned by the organization.
    * **Restrict access via {% data variables.product.pat_v1_plural %}**: {% data variables.product.pat_v1_caps_plural %} cannot access resources owned by the organization. SSH keys created by {% data variables.product.pat_v1_plural %} will continue to work.
 1. Click **Save**.

content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md

@@ -31,6 +31,8 @@ If you put your README file in your repository's hidden `.github`, root, or `doc
 
 If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
 
+When your README is viewed on GitHub, any content beyond 500 KiB will be truncated.
+
 {% data reusables.profile.profile-readme %}
 
 ## Auto-generated table of contents for README files

data/features/tabbed-pat-settings-ui.yml

@@ -0,0 +1,6 @@
+# Reference: #52010
+# UI change for tabbed settings pages for enterprise and orgs.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.15'

src/audit-logs/lib/config.json

@@ -3,5 +3,5 @@
     "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
     "apiRequestEvent": "This event is only available via audit log streaming."
   },
-  "sha": "1edaa64f5136ea30fb0de04ac67d03a25120684d"
+  "sha": "0da185a95ffe0bea6a17eb08ac06a03b5729e751"
 }

src/ghes-releases/lib/enterprise-dates.json

@@ -133,11 +133,11 @@
   },
   "3.9": {
     "releaseDate": "2023-06-08",
-    "deprecationDate": "2024-07-09"
+    "deprecationDate": "2024-07-26"
   },
   "3.10": {
     "releaseDate": "2023-08-08",
-    "deprecationDate": "2024-08-29"
+    "deprecationDate": "2024-09-24"
   },
   "3.11": {
     "releaseDate": "2023-11-14",
@@ -156,7 +156,7 @@
     "deprecationDate": "2025-08-27"
   },
   "3.15": {
-    "releaseDate": "2024-10-29",
+    "releaseDate": "2024-11-12",
     "deprecationDate": "2025-11-19"
   },
   "3.16": {

src/links/components/LinkPreviewPopover.tsx

@@ -308,7 +308,13 @@ function fillPopover(
         // All a.href attributes are always full absolute URLs, as a string.
         // We assume that the "product landing page" is the first
         // portion of all links.
-        productHeadLink.href = linkURL.pathname.split('/').slice(0, 3).join('/')
+        const regex = /^\/(?<lang>\w{2}\/)?(?<version>[\w-]+@[\w-.]+\/)?(?<product>[\w-]+\/)?/
+        const match = regex.exec(linkURL.pathname)
+        if (match?.groups) {
+          const { lang, version, product } = match.groups
+          const productURL = [lang, version, product].map((n) => n || '').join('')
+          productHeadLink.href = `${linkURL.origin}/${productURL}`
+        }
         productHead.style.display = 'block'
       }
     } else {