Repo sync

.github/workflows/close-prs-without-help-wanted-issue.yml

@@ -81,7 +81,7 @@ jobs:
               owner,
               repo,
               issue_number: pull_number,
-              body: "Please don't raise pull requests against an existing issue that another user has raised until it's been marked with a `help wanted` label. We need to properly assess all issues before we can accept community contributions, and determine whether it's something we need to fix internally, or how many articles are affected and what the scope of the fix will be. For now, we're going to close this pull request.",
+              body: "> [!WARNING]\n> **This pull request was closed automatically.**\n>\n> Please don't raise pull requests against an existing issue that another user has raised until it's been marked with a `help wanted` label. We need to properly assess all issues before we can accept community contributions, and determine whether it's something we need to fix internally, or how many articles are affected and what the scope of the fix will be. For now, we're going to close this pull request.",
             })
 
             await github.rest.pulls.update({

.github/workflows/copy-api-issue-to-internal.yml

@@ -67,11 +67,12 @@ jobs:
           OLD_ISSUE: ${{ github.event.issue.html_url }}
 
       - name: Comment on the new issue
-        run: gh issue comment $NEW_ISSUE --body "This issue was originally opened in the open source repo as $OLD_ISSUE"
+        run: gh issue comment "$NEW_ISSUE" --body "This issue was originally opened in the open source repo as $OLD_ISSUE. @$ISSUE_LABELER marked it for an internal fix."
         env:
           GITHUB_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}
           NEW_ISSUE: ${{ env.NEW_ISSUE }}
           OLD_ISSUE: ${{ github.event.issue.html_url }}
+          ISSUE_LABELER: ${{ github.event.sender.login }}
 
       - name: Check out repo
         if: ${{ failure() && github.event_name != 'workflow_dispatch' }}

content/actions/reference/runners/self-hosted-runners.md

@@ -132,11 +132,16 @@ To turn off automatic software updates and install software updates yourself, sp
 
 If you disable automatic updates, you must still update your runner version regularly. New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software. The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
 
-If you disable automatic updates, you will be required to update your runner version within 30 days of a new version being made available. You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). For more information, see [AUTOTITLE](/subscriptions-and-notifications/get-started/configuring-notifications#about-custom-notifications).
+If you disable automatic updates, you must update your runner version within {% ifversion fpt or ghec %}63{% else %}30{% endif %} days of a newer version being made available. You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). For more information, see [AUTOTITLE](/subscriptions-and-notifications/get-started/configuring-notifications#about-custom-notifications).
+
+{% ifversion fpt or ghec %}
+The date a runner version becomes available for updates can differ from its release date. To check a version's end-of-life schedule, use the REST API endpoint for your [repository](/rest/actions/self-hosted-runners#get-runner-version-end-of-life-schedule-for-a-repository) or [organization](/rest/actions/self-hosted-runners#get-runner-version-end-of-life-schedule-for-an-organization){% ifversion ghec %}, or for your [enterprise](/rest/actions/self-hosted-runners#get-runner-version-end-of-life-schedule-for-an-enterprise){% endif %}. The `registration_deprecates_at` date is when you can no longer register a runner using that version. The `runtime_deprecates_at` date is when runners on that version can no longer receive jobs. A `null` value means no date is currently scheduled.
+{% endif %}
 
 For instructions on how to install the latest runner version, see the installation instructions for [the latest release](https://github.com/actions/runner/releases).
 
-{% data reusables.actions.self-hosted-runner-update-warning %}
+> [!WARNING]
+> {% data reusables.actions.self-hosted-runner-update-warning %}
 
 ### Webhooks for autoscaling
 

content/actions/tutorials/use-actions-runner-controller/troubleshoot.md

@@ -159,7 +159,8 @@ A `401 Unauthorized` error when attempting to obtain an access token for a {% da
 
 ## Runner updates
 
-{% data reusables.actions.self-hosted-runner-update-warning %}
+> [!WARNING]
+> {% data reusables.actions.self-hosted-runner-update-warning %}
 
 Validate that your runner software version and/or custom runner image(s) in use are running the latest version.
 

content/billing/how-tos/set-up-budgets.md

@@ -129,18 +129,16 @@ As the owner of an enterprise or organization account, or as a billing manager,
 1. Under "Budget Type" select **Product-level budget**, **SKU-level budget**, or **Bundled {% data variables.product.prodname_ai_credits_short %} budget**.
 
    * **Product-level budget**: Limits spending on a single product (for example, {% data variables.product.prodname_codespaces %}).
-   * **SKU-level budget**: Limits spending on a specific SKU within a product (for example, {% data variables.product.prodname_GH_secret_protection %} within {% data variables.product.prodname_GHAS %}).
-   * **Bundled {% data variables.product.prodname_ai_credits_short %} budget**: Limits spending across all SKUs that consume {% data variables.product.prodname_ai_credits_short %}, including {% data variables.product.prodname_copilot_short %}, {% data variables.copilot.copilot_cloud_agent %}, {% data variables.product.prodname_spark_short %}, and {% data variables.product.prodname_AS %} AI features. Available where overage spend is enabled.
-
-   To limit spending on AI Scan and agentic autofix, select **SKU-level budget**. In the product dropdown, select **{% data variables.product.prodname_AS %}**, then in the SKU dropdown, select **Code Security AI Credits**.
+   * **SKU-level budget**: Limits spending on a specific SKU within a product, such as {% data variables.copilot.copilot_code-review_short %}, {% data variables.product.prodname_secret_protection %} {% data variables.product.prodname_ai_credits_short %}, or {% data variables.product.prodname_GH_secret_protection %} within {% data variables.product.prodname_GHAS %}. For AI Scan and agentic autofix, select {% data variables.product.prodname_AS %} and the **Code Security AI Credits** SKU.
+   * **Bundled {% data variables.product.prodname_ai_credits_short %} budget**: Limits total overage spending across all SKUs that consume {% data variables.product.prodname_ai_credits_short %}, including {% data variables.product.prodname_copilot_short %}, {% data variables.copilot.copilot_cloud_agent %}, {% data variables.product.prodname_spark_short %}, and {% data variables.product.prodname_AS %} AI features. Each SKU uses the shared {% data variables.product.prodname_ai_credits_short %} allowance before generating overage. After the allowance is exhausted, overage from every SKU counts toward the applicable **All {% data variables.product.prodname_ai_credits_short %}** budget. To also limit overage for a specific SKU, create a SKU-level budget for that SKU. Available where overage spend is enabled.
 
 1. Under "Budget scope", set the scope of spending for this budget.
 
    * **Enterprise**: Tracks spending across all organizations, repositories, and cost centers in the enterprise.
    * **Organization**: Tracks spending for all repositories in the organization.
    * **Cost center**: Tracks spending for a single cost center.
-   * **Users**: Sets a per-user budget. Available when you select **Bundled {% data variables.product.prodname_ai_credits_short %} budget** as the budget type. 
-     * Leave the user field empty to create a universal budget that applies to all {% data variables.product.prodname_copilot_short %}-licensed users. 
+   * **Users**: Sets a per-user budget. Available when you select **Bundled {% data variables.product.prodname_ai_credits_short %} budget** as the budget type.
+     * Leave the user field empty to create a universal budget that applies to all {% data variables.product.prodname_copilot_short %}-licensed users.
      * Select a cost center to create a user-level budget that applies to every user in that cost center. This sets one per-user amount for all current and future members, and overrides the universal budget for them.
      * Select a specific user to create an individual budget that overrides both the universal budget and any cost center user-level budget for that user.
 

content/billing/reference/product-and-sku-names.md

@@ -88,16 +88,20 @@ For **SkuPricing** budgets or to query usage by SKU, use one of the following va
 ### {% data variables.product.prodname_copilot %} SKUs
 
 * `coding_agent_ai_credit` - Copilot Cloud Agent
+* `code_review_premium_request` - {% data variables.copilot.copilot_code-review_short %} {% data variables.product.prodname_ai_credits_short %}
 * `copilot_ai_credit` - {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %}
 * `copilot_enterprise` - Copilot Enterprise
 * `copilot_for_business` - Copilot for Business
 * `copilot_standalone` - Copilot standalone
 
 ### {% data variables.product.prodname_GH_advanced_security %} SKUs
 
+* `code_security_ai_unit` - {% data variables.product.prodname_code_security %} {% data variables.product.prodname_ai_credits_short %}
+* `deep_security_research_ai_unit` - Deep Security Research {% data variables.product.prodname_ai_credits_short %}
 * `ghas_code_security_licenses` - Code Security
 * `ghas_licenses` - Advanced Security
 * `ghas_secret_protection_licenses` - Secret Protection
+* `secret_protection_ai_unit` - {% data variables.product.prodname_secret_protection %} {% data variables.product.prodname_ai_credits_short %}
 
 ### {% data variables.product.prodname_code_quality %} SKUs
 

content/code-security/concepts/code-scanning/ai-powered-security-detections.md

@@ -68,6 +68,7 @@ You can use the thumbs up or thumbs down control to provide feedback and help im
 
 * AI Scan findings cannot yet be used in rulesets to enforce merge requirements.
 * AI Scan does not run on pull requests from forks or pull requests created by {% data variables.product.prodname_dependabot %}.
+* Self-hosted runners are not supported.
 * Detection categories and supported languages may change as the feature evolves.
 * As with any AI-based tool, AI Scan findings may include false positives. Use the feedback mechanism to report inaccurate results.
 

content/code-security/tutorials/trialing-github-advanced-security/trial-advanced-security.md

@@ -36,15 +36,11 @@ Your payment method does not affect whether you can start a trial. However, you
 To set up a trial of {% data variables.product.prodname_GHAS %} using this method, you must meet the following criteria:
 
 * You are an owner of an enterprise account. See [AUTOTITLE](/enterprise-cloud@latest/admin/concepts/enterprise-fundamentals/enterprise-accounts).
-* You pay by credit card or PayPal.
-* You have not previously purchased {% data variables.product.prodname_GHAS %} and do not currently have a paid license.
 * You are not already using metered billing for {% data variables.product.prodname_GHAS %}.
 * If you have had a previous {% data variables.product.prodname_GHAS %} trial, you have had no more than one previous trial. That trial ended at least 180 days ago.
-* Your enterprise has 300 or fewer seats.
 
 > [!TIP]
-> * **No enterprise account?** Start a trial of {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GHAS %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/overview/setting-up-a-trial-of-github-enterprise-cloud).
-> * **Pay by invoice:** Contact {% data variables.contact.contact_enterprise_sales %} to arrange a trial.
+> **No enterprise account?** Start a trial of {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GHAS %}. See [AUTOTITLE](/enterprise-cloud@latest/admin/overview/setting-up-a-trial-of-github-enterprise-cloud).
 
 {% endif %}
 

content/copilot/concepts/enterprise/opentelemetry.md

@@ -23,6 +23,8 @@ When you enable OTel monitoring, you can send data from users' {% data variables
 * **Metrics** are numeric measurements that help you identify patterns over time. For example, token usage metrics track the number of input and output tokens used in model calls.
 * **Events** record individual actions at a specific point in time. For example, an edit feedback event records whether a user accepted or rejected an agent edit.
 
+For configuration options, exported signals, and attributes, see [AUTOTITLE](/copilot/reference/enterprise-administrators/opentelemetry-reference).
+
 By default, the data does not include directly identifying attributes, prompts, responses, tool arguments, tool results, or raw policy details. Enterprise administrators can independently enable the following capture classes through managed settings:
 
 * **Identity** adds the authenticated {% data variables.product.prodname_copilot_short %} account name, local operating-system account, and machine name. This lets you attribute activity without collecting conversation or tool content.
@@ -56,4 +58,3 @@ For more details of how OpenTelemetry is used across clients, see:
 
 * [Monitor agent usage with OpenTelemetry](https://code.visualstudio.com/docs/agents/guides/monitoring-agents) in the {% data variables.product.prodname_vscode_shortname %} documentation
 * [AUTOTITLE](/copilot/how-tos/copilot-sdk/observability/opentelemetry)
-* [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference#opentelemetry-monitoring)

content/copilot/how-tos/copilot-cli/automate-copilot-cli/run-cli-programmatically.md

@@ -41,7 +41,7 @@ To use {% data variables.copilot.copilot_cli_short %} programmatically you can d
 * **Always give minimal permissions** — use the `--allow-tool=[TOOLS...]` and `--allow-url=[URLs...]` command-line options to give {% data variables.product.prodname_copilot_short %} permission to use only the tools and access that are necessary to complete the task. Avoid using overly permissive options (such as `--allow-all`) unless you are working in a sandbox environment. For more information, see [AUTOTITLE](/copilot/concepts/about-cloud-and-local-sandboxes).
 * **Consider `--assisted-approval`** when you can't predict in advance which tools a task will need. A model-based safety review can approve eligible permission requests without you granting blanket permissions. Existing permission rules still apply, and requests that still require your approval are denied in unattended runs. For more information, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-programmatic-reference#using-assisted-permissions).
 * **Use `-s` (silent)** when capturing output. This suppresses session metadata so you get clean text.
-* **Use `--no-ask-user`** to prevent the agent from attempting to ask clarifying questions.
+* **Use `--no-ask-user`** to turn off the interactive clarifying-question prompt, since there's no user available to respond to it in an automated run. The agent can still ask questions as part of its regular text replies.
 * **Set a model explicitly** with `--model` for consistent behavior across environments.
 
 See [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-programmatic-reference) for options that are particularly useful when running {% data variables.copilot.copilot_cli_short %} programmatically.

content/copilot/how-tos/use-copilot-agents/use-dynamic-workflows.md

@@ -229,7 +229,7 @@ If you are running, or have run, a dynamic workflow in the current session, a **
 
 If you have enabled OpenTelemetry (OTel), you can inspect workflow activity in your traces. A workflow creates an `invoke_workflow` span each time it runs or resumes, with its agents' activity linked to it.
 
-For configuration in {% data variables.copilot.copilot_cli_short %}, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference#opentelemetry-monitoring).
+For configuration options and exported telemetry data, see [AUTOTITLE](/copilot/reference/enterprise-administrators/opentelemetry-reference).
 
 ### Resuming a run