Merge branch 'main' into artifact

Author: Sharra-writes

assets/images/help/copilot/code-review/xcode-ccr-button.png

@@ -39,8 +39,11 @@ shortTitle: Merge multiple accounts
 1. [Transfer any repositories](/repositories/creating-and-managing-repositories/transferring-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
 1. [Update the remote URLs](/get-started/git-basics/managing-remote-repositories) in any local clones of the repositories that were moved.
 1. [Delete the account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account) you no longer want to use.
-1. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)
+1. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping.
+   > [!NOTE]
+   > There are additional requirements for commits to count as contributions that you will need to ensure are met. See [AUTOTITLE](/account-and-profile/reference/why-are-my-contributions-not-showing-up-on-my-profile#contribution-criteria-for-commits).
 
 ## Further reading
 
 * [AUTOTITLE](/get-started/learning-about-github/types-of-github-accounts)
+* [AUTOTITLE](/account-and-profile/reference/best-practices-for-leaving-your-company)

assets/images/help/copilot/code-review/xcode-review-popup.png

@@ -148,11 +148,11 @@ For more information on how to use context syntax, see [AUTOTITLE](/actions/lear
 
 **Required** Configures the path to the action's code and the runtime used to execute the code.
 
-### Example: Using Node.js v20
+### Example: Using Node.js v24
 
 ```yaml
 runs:
-  using: 'node20'
+  using: 'node24'
   main: 'main.js'
 ```
 
@@ -161,6 +161,7 @@ runs:
 **Required** The runtime used to execute the code specified in [`main`](#runsmain).
 
 * Use `node20` for Node.js v20.
+* Use `node24` for Node.js v24.
 
 ### `runs.main`
 
@@ -177,7 +178,7 @@ In this example, the `pre:` action runs a script called `setup.js`:
 
 ```yaml
 runs:
-  using: 'node20'
+  using: 'node24'
   pre: 'setup.js'
   main: 'index.js'
   post: 'cleanup.js'
@@ -204,7 +205,7 @@ In this example, the `post:` action runs a script called `cleanup.js`:
 
 ```yaml
 runs:
-  using: 'node20'
+  using: 'node24'
   main: 'index.js'
   post: 'cleanup.js'
 ```

content/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts.md

@@ -65,17 +65,17 @@ curl --include -H "Authorization: Bearer TOKEN" \
 If there are more than 100 results, the `link` header will include URLs to fetch the next, first, and previous pages of results.
 
 ```text
-link: <{% data variables.product.rest_url %}/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42NjQzODMzNTk5MjdlKzEyfDloQzBxdURzaFdVbVlLWjkxRU9mNXc%3D&before=>; rel="next",
-<{% data variables.product.rest_url %}/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=>; rel="first",
-<{% data variables.product.rest_url %}/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=MS42Njc4NDA2MjM4MzNlKzEyfExqeG5sUElvNEZMbG1XZHA5akdKTVE%3D>; rel="prev"
+link: <{% data variables.product.rest_url %}/enterprises/13827/audit-log?phrase%3A2022-11-01=&per_page=100&after=MS42NjQzODMzNTk5MjdlKzEyfDloQzBxdURzaFdVbVlLWjkxRU9mNXc%3D&before=>; rel="next",
+<{% data variables.product.rest_url %}/enterprises/13827/audit-log?phrase%3A2022-11-01=&per_page=100&after=&before=>; rel="first",
+<{% data variables.product.rest_url %}/enterprises/13827/audit-log?phrase%3A2022-11-01=&per_page=100&after=&before=MS42Njc4NDA2MjM4MzNlKzEyfExqeG5sUElvNEZMbG1XZHA5akdKTVE%3D>; rel="prev"
 ```
 
 Copy the corresponding pagination link into your next request. For example:
 
 ```shell
 curl -I -H "Authorization: Bearer TOKEN" \
 --request GET \
-"{% data variables.product.rest_url %}/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42Njc4NDA2MjM5NDFlKzEyfHRYa3AwSkxUd2xyRjA5bWxfOS1RbFE%3D&before="
+"{% data variables.product.rest_url %}/enterprises/13827/audit-log?phrase%3A2022-11-01=&per_page=100&after=MS42Njc4NDA2MjM5NDFlKzEyfHRYa3AwSkxUd2xyRjA5bWxfOS1RbFE%3D&before="
 ```
 
 {% endif %}

content/actions/reference/workflows-and-actions/metadata-syntax.md

@@ -43,7 +43,7 @@ When the index rebuild is complete, all the search indexes should show green and
 
 ## Changing the number of repair workers
 
-By default, the number of index repair workers is set to the number of CPU cores divided by 8 (with an upper bound of 8). To speed up the index rebuild, you can adjust the worker count. However, before doing so, you should consider the potential impact to the load.
+By default, the number of index repair workers is set to the number of CPU cores divided by 8 (with an upper bound of 16). To speed up the index rebuild, you can adjust the worker count. However, before doing so, you should consider the potential impact to the load.
 
 {% data reusables.enterprise_installation.ssh-into-instance %}
 1. To change the number of workers, enter the following command.

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md

@@ -96,10 +96,7 @@ There are two different ways to pay for licenses.
   * Purchase a specific number of {% data variables.product.prodname_GHAS_cs_or_sp %} licenses that last for a defined period, typically at least a year, see {% ifversion fpt or ghec %}[AUTOTITLE](/billing/how-tos/products/add-advanced-security){% elsif ghes %}[AUTOTITLE](/enterprise-cloud@latest/billing/how-tos/products/add-advanced-security) in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}.
   * If the usage of {% data variables.product.prodname_AS %} by active committers exceeds the number of licenses purchased, you need to purchase additional licenses to cover this overage usage.
 
-<!-- expires 2025-08-31 -->
-<!--This versioning is not needed once the related EDI PR for this article is merged (#57129).-->
-{% ifversion fpt or ghec %}To view your current license usage, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage).{% endif %}
-<!-- end expires 2025-08-31 -->
+To view your current license usage, see [AUTOTITLE](/billing/managing-billing-for-your-products/viewing-your-product-usage).
 
 ### Understanding usage
 

content/admin/upgrading-your-instance/performing-an-upgrade/preparing-for-the-elasticsearch-upgrade.md

@@ -37,7 +37,7 @@ To ensure your cost centers reflect spending as intended, it's important to unde
 ### {% data variables.product.prodname_copilot %}
 
 * If a user belongs to a cost center, all usage associated with the user is charged to the cost center.
-* If a user does not belong to any cost center, if the organization that provides the user their {% data variables.product.prodname_copilot_short %} license belongs to a cost center, all usage associated with the user is charged to the cost center.
+* If a user does not belong to any cost center but the organization that is billed for the {% data variables.product.prodname_copilot_short %} license does, all usage associated with the user is charged to that cost center.
 * If the user receives access to {% data variables.product.prodname_copilot_short %} through **multiple organizations**, only one of the organizations is billed, and any cost center containing that organization is charged accordingly. See [AUTOTITLE](/copilot/managing-copilot/managing-copilot-for-your-enterprise/managing-the-copilot-subscription-for-your-enterprise/about-billing-for-github-copilot-in-your-enterprise#about-seat-assignment-for-copilot-in-your-enterprise).
 
 ### {% data variables.product.prodname_GH_cs_and_sp %}

content/billing/concepts/product-billing/github-advanced-security.md

@@ -38,10 +38,7 @@ Adopting a few key best practices can help you participate successfully in a cam
 
 ### Notification settings
 
-To receive email updates about security campaigns in repositories you have write access to, make sure that you:
-
-* **Watch** all repositories that you have write access to.
-* **Subscribe** to notifications for "All activity" or "Security alerts".
+You'll automatically receive email updates about security campaigns for any repositories you have **write** access to, so you can stay informed about relevant updates.
 
 ### View campaign details
 

content/billing/reference/cost-center-allocation.md

@@ -20,8 +20,8 @@ topics:
 When a campaign targets security alerts in a repository that you have write access to, you can navigate to the list of repository alerts in the campaign.
 
 * Display the **Security** tab for the repository and click one of the campaigns under "Campaigns" in the sidebar.
-* If you have enabled email notifications for "All activity" or "Security alerts" in the repository, click **View security campaign** in the campaign email.
 * If you have write access to more than one repository in the organization, display the **Security** tab for the organization and click one of the campaigns under "Campaigns" in the sidebar.
+* Alternatively, click **View security campaign** in the campaign's email notification.
 
 This view shows the alerts in the current repository for a campaign called "SQL injection (CWE-89)" (highlighted gray) that is managed by "octocat" (outlined in dark orange).