Merge pull request #38758 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/data-residency/network-details-for-ghecom.md

@@ -130,8 +130,6 @@ You must allow:
 
 ### Required in Australia
 
-* 20.213.236.72/29
-* 20.53.178.216/29
 * 20.213.241.72/29
 * 20.11.90.48/29
 * 20.5.34.240/28

content/billing/managing-billing-for-your-products/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md

@@ -36,9 +36,9 @@ You can view the current license limits and usage for your enterprise.
    * If you have a volume/subscription license, the number of licenses **available** to use is also displayed.
    * If you run out of licenses, for volume/subscription only, the section is red and reports "Limit exceeded." You should either reduce your use or purchase more licenses.
 
-1. Optionally, to see a detailed breakdown of usage per organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}, in the "{% data variables.product.prodname_GHAS %}" section click **More details**.
+1. Optionally, to see a detailed breakdown of usage per organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}, in the "{% data variables.product.prodname_AS %}" section click **More details**.
 
-   In the "{% data variables.product.prodname_GHAS %}" section, you can see a summary of your current license usage, as well as the number of committers and unique committers for each organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}. The organizations{% ifversion secret-scanning-user-owned-repos %} and user namespaces{% endif %} in the billing table are sorted by the highest number of unique committers in descending order.
+   In the "{% data variables.product.prodname_AS %}" section, you can see a summary of your current license usage, as well as the number of committers and unique committers for each organization{% ifversion secret-scanning-user-owned-repos %} and user namespace when using {% data variables.product.prodname_emus %}{% endif %}. The organizations{% ifversion secret-scanning-user-owned-repos %} and user namespaces{% endif %} in the billing table are sorted by the highest number of unique committers in descending order.
 
 1. Optionally, to see a detailed breakdown of usage by repositories within an organization, click an organization name to display the "Global code security settings" for the organization.
 
@@ -77,7 +77,7 @@ You can view the organization account's current license limits and usage.
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.billing_plans_or_licensing %}
 
-   The "{% data variables.product.prodname_GHAS %}" section shows details of the current usage.
+   The "{% data variables.product.prodname_AS %}" section shows details of the current usage.
 
 {% endif %}
 
@@ -88,14 +88,14 @@ You can view the organization account's current license limits and usage.
 
 ## Downloading {% data variables.product.prodname_AS %} license usage information
 
-You can download a CSV file with {% data variables.product.prodname_GHAS %} license usage information at both the {% data variables.enterprise.enterprise_and_org %} level. The CSV file contains information about each {% data variables.product.prodname_AS %} license that is in use, including:
+You can download a CSV file with details of paid use of {% data variables.product.prodname_GHAS %} products at both the {% data variables.enterprise.enterprise_and_org %} level. The CSV file contains information about each {% data variables.product.prodname_AS %} license that is in use, including:
 
 * The username of the person using the {% data variables.product.prodname_GHAS_cs_or_sp %} license
 * The {% data variables.product.prodname_GH_cs_and_sp %}-enabled repositories where commits were made
 * The organizations{% ifversion secret-scanning-user-owned-repos %}{% ifversion ghec %} and user namespaces for {% data variables.product.prodname_emus %}{% endif %}{% endif %} that people using licenses belong to
 * The most recent commit dates and associated email addresses
 
-You can use this information for insights into your {% data variables.product.prodname_AS %} usage, such as which members of your enterprise are using a license or how licenses are being consumed across your organizations.
+You can use this information for insights into your paid use of {% data variables.product.prodname_AS %}, such as which members of your enterprise are using a license or how licenses are being consumed across your organizations.
 
 You can download a CSV report of license usage through the {% data variables.product.github %} user interface or the REST API.
 
@@ -160,7 +160,7 @@ You can download a CSV report of license usage through the {% data variables.pro
 
 ## Using the REST API to download license and metered usage
 
-You can retrieve {% data variables.product.prodname_AS %} usage information via the billing API.
+You can retrieve information on paid use of {% data variables.product.prodname_AS %} with the billing API.
 
 {% ifversion fpt or ghec %}
 

content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md

@@ -38,7 +38,7 @@ Additionally, items are also marked as updated when field values in your project
 
 When you enable automatic archiving for issues or pull requests, items in your project that already meet your criteria will also be archived. There may be some delay in archiving large numbers of items that already meet the criteria.
 
-{% ifversion projects-single-limit %}Your project can contain up to {% data variables.projects.item_limit %} items across both active views and the archive page. Once that limit has been reached, you will need to delete items from your project to free up more space.{% else %} Projects also have a limit on the number of archived items they can contain. Your project can contain up to {% data variables.projects.archived_item_limit %} archived items.{% endif %} For more information on permanently deleting items, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project#deleting-items).
+{% ifversion projects-single-limit %}Your project can contain up to {% data variables.projects.item_limit %} items across both active views and the archive page. Once that limit has been reached, you will need to delete items from your project to free up more space.{% else %} Projects also have a limit on the number of archived items they can contain. Your project can contain up to {% data variables.projects.legacy_archived_item_limit %} archived items.{% endif %} For more information on permanently deleting items, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project#deleting-items).
 
 ## Configuring automatic archiving in your project
 

content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md

@@ -12,7 +12,7 @@ allowTitleToDifferFromFilename: true
 ---
 
 > [!NOTE]
-> * If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
+> * If the project you are migrating contains more than {% data variables.projects.legacy_item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.legacy_archived_item_limit %} items is reached, additional items will not be migrated.
 > * Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view#showing-and-hiding-fields).
 > * Automation will not be migrated.
 > * Triage, archive, and activity will not be migrated.

content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md

@@ -13,7 +13,7 @@ allowTitleToDifferFromFilename: true
 ---
 
 > [!NOTE]
-> A project can contain a maximum of {% data variables.projects.item_limit %} items {% ifversion projects-single-limit %} across both active views and the archive page{% else %}and {% data variables.projects.archived_item_limit %} archived items{% endif %}. To learn more about automatically archiving items when they meet specific criteria, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically).
+> A project can contain a maximum of{% ifversion projects-single-limit %} {% data variables.projects.item_limit %} items across both active views and the archive page{% else %} {% data variables.projects.legacy_item_limit %} items and {% data variables.projects.legacy_archived_item_limit %} archived items{% endif %}. To learn more about automatically archiving items when they meet specific criteria, see [AUTOTITLE](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically).
 
 ## Adding issues and pull requests to a project
 

content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md

@@ -13,7 +13,7 @@ allowTitleToDifferFromFilename: true
 ---
 
 > [!NOTE]
-> A project can contain a maximum of {% data variables.projects.item_limit %} items {% ifversion projects-single-limit %}across both active views and archive page{% else %} and {% data variables.projects.archived_item_limit %} archived items{% endif %}.
+> A project can contain a maximum of{% ifversion projects-single-limit %} {% data variables.projects.item_limit %} items across both active views and the archive page{% else %} {% data variables.projects.legacy_item_limit %} items and {% data variables.projects.legacy_archived_item_limit %} archived items{% endif %}.
 
 ## Archiving items
 

data/variables/projects.yml

@@ -20,8 +20,9 @@ project_v2_and_v1: '{% data variables.projects.project_v2 %}{% ifversion project
 projects_v2_and_v1_if_create: '{% data variables.projects.projects_v2 %}{% ifversion projects-v1-can-create %} and {% data variables.projects.projects_v1_boards %}{% endif %}'
 
 # Limits
+legacy_item_limit: '1,200'
 item_limit: '50,000'
-archived_item_limit: '10,000'
+legacy_archived_item_limit: '10,000'
 issue_type_limit: '25'
 sub-issue_limit: '100'
 

src/audit-logs/data/fpt/organization.json

@@ -3299,6 +3299,16 @@
     "description": "A request to bypass secret scanning push protection was approved by a user.",
     "docs_reference_links": "/code-security/secret-scanning/push-protection-for-repositories-and-organizations#managing-requests-to-bypass-push-protection"
   },
+  {
+    "action": "secret_scanning_push_protection_request.cancel",
+    "description": "A user canceled a request to bypass secret scanning push protection.",
+    "docs_reference_links": "/code-security/secret-scanning/working-with-push-protection#requesting-bypass-privileges-when-working-with-the-command-line"
+  },
+  {
+    "action": "secret_scanning_push_protection_request.complete",
+    "description": "A user pushed a commit containing a secret for which there is an approved secret scanning push protection bypass request.",
+    "docs_reference_links": "/code-security/secret-scanning/working-with-push-protection#requesting-bypass-privileges-when-working-with-the-command-line"
+  },
   {
     "action": "secret_scanning_push_protection_request.deny",
     "description": "A request to bypass secret scanning push protection was denied by a user.",

src/audit-logs/data/ghec/enterprise.json

@@ -349,6 +349,16 @@
     "description": "The trial of GitHub Enterprise Cloud expired.",
     "docs_reference_links": "/admin/overview/setting-up-a-trial-of-github-enterprise-cloud"
   },
+  {
+    "action": "business.github_models_billing_disabled",
+    "description": "GitHub Models billing was disabled for the business.",
+    "docs_reference_links": "N/A"
+  },
+  {
+    "action": "business.github_models_billing_enabled",
+    "description": "GitHub Models billing was enabled for the business.",
+    "docs_reference_links": "N/A"
+  },
   {
     "action": "business.import_license_usage",
     "description": "License usage information was imported from a GitHub Enterprise Server instance to an enterprise account on GitHub.com.",
@@ -4039,6 +4049,16 @@
     "description": "A request to bypass secret scanning push protection was approved by a user.",
     "docs_reference_links": "/code-security/secret-scanning/push-protection-for-repositories-and-organizations#managing-requests-to-bypass-push-protection"
   },
+  {
+    "action": "secret_scanning_push_protection_request.cancel",
+    "description": "A user canceled a request to bypass secret scanning push protection.",
+    "docs_reference_links": "/code-security/secret-scanning/working-with-push-protection#requesting-bypass-privileges-when-working-with-the-command-line"
+  },
+  {
+    "action": "secret_scanning_push_protection_request.complete",
+    "description": "A user pushed a commit containing a secret for which there is an approved secret scanning push protection bypass request.",
+    "docs_reference_links": "/code-security/secret-scanning/working-with-push-protection#requesting-bypass-privileges-when-working-with-the-command-line"
+  },
   {
     "action": "secret_scanning_push_protection_request.deny",
     "description": "A request to bypass secret scanning push protection was denied by a user.",

src/audit-logs/data/ghec/organization.json

@@ -3299,6 +3299,16 @@
     "description": "A request to bypass secret scanning push protection was approved by a user.",
     "docs_reference_links": "/code-security/secret-scanning/push-protection-for-repositories-and-organizations#managing-requests-to-bypass-push-protection"
   },
+  {
+    "action": "secret_scanning_push_protection_request.cancel",
+    "description": "A user canceled a request to bypass secret scanning push protection.",
+    "docs_reference_links": "/code-security/secret-scanning/working-with-push-protection#requesting-bypass-privileges-when-working-with-the-command-line"
+  },
+  {
+    "action": "secret_scanning_push_protection_request.complete",
+    "description": "A user pushed a commit containing a secret for which there is an approved secret scanning push protection bypass request.",
+    "docs_reference_links": "/code-security/secret-scanning/working-with-push-protection#requesting-bypass-privileges-when-working-with-the-command-line"
+  },
   {
     "action": "secret_scanning_push_protection_request.deny",
     "description": "A request to bypass secret scanning push protection was denied by a user.",