Merge pull request #45564 from github/repo-sync

Repo sync

Author: docs-bot

assets/images/help/copilot/copilot-sdk/features-agent-loop-diagram-1.png

@@ -22,11 +22,13 @@ Use of {% data variables.product.prodname_code_quality_short %} incurs three typ
 
 {% data variables.product.prodname_code_quality_short %} scans run as {% data variables.product.prodname_actions %} workflows and consume {% data variables.product.prodname_actions %} minutes, unless you use self-hosted runners. See [AUTOTITLE](/billing/concepts/product-billing/github-actions).
 
+In a detailed usage report, you can identify usage from {% data variables.product.prodname_code_quality_short %} scans by filtering the `workflow_path` field for `{% data variables.code-quality.workflow_name_billing %}`.
+
 ### {% data variables.product.prodname_ai_credits %}
 
 {% data variables.product.prodname_code_quality_short %} features that use AI models consume {% data variables.product.prodname_ai_credits_short %} from your shared {% data variables.product.prodname_ai_credits_short %} pool, rather than a separate {% data variables.product.prodname_code_quality_short %} allowance. Each interaction is priced based on the number of tokens consumed, where 1 {% data variables.product.prodname_ai_credit_singular %} = {% data variables.product.prodname_ai_credits_value %}. 
 
-{% data reusables.code-quality.model-usage %} 
+{% data reusables.code-quality.model-usage %}
 
 For more information about how {% data variables.product.prodname_ai_credits_short %} work, see [AUTOTITLE](/copilot/concepts/billing/usage-based-billing-for-organizations-and-enterprises).
 

assets/images/help/copilot/copilot-sdk/features-agent-loop-diagram-2.png

@@ -54,7 +54,4 @@ What confirms the change depends on the level you disabled it at.
 
 **At the organization level**, open the organization's "{% data variables.code-quality.code_quality_ui %}" settings page and check that **Repository access** shows your selection (for example, **No repositories**) and that **Enforce access** is on if you enforced it. The organization-level {% data variables.product.prodname_code_quality_short %} dashboard also stops showing data for the affected repositories. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/explore-code-quality).
 
-**At the repository level**, the repository's "{% data variables.code-quality.code_quality_ui %}" settings page shows that {% data variables.product.prodname_code_quality_short %} analysis is disabled. If organization or enterprise enforcement applies, the page also shows a message that a policy prevents changing the {% data variables.product.prodname_code_quality_short %} setting. No new {% data variables.product.prodname_code_quality_short %} runs start on later pull requests or pushes; on the **Actions** tab, these runs are labeled by trigger, for example "{% data variables.product.prodname_code_quality_short %}: push on main".
-
-> [!NOTE]
-> These runs use the workflow name {% data variables.product.prodname_codeql %}, the same name {% data variables.product.prodname_code_scanning %} uses, so you can't reliably tell {% data variables.product.prodname_code_quality_short %} and {% data variables.product.prodname_code_scanning %} runs apart by workflow name. Identify {% data variables.product.prodname_code_quality_short %} runs by their {% data variables.product.prodname_actions %} label instead, for example "{% data variables.product.prodname_code_quality_short %}: push on main".
+**At the repository level**, the repository's "{% data variables.code-quality.code_quality_ui %}" settings page shows that {% data variables.product.prodname_code_quality_short %} analysis is disabled. If organization or enterprise enforcement applies, the page also shows a message that a policy prevents changing the setting. No new runs start on later pull requests or pushes. On the **Actions** tab, identify existing {% data variables.product.prodname_code_quality_short %} runs by the actor `{% data variables.code-quality.workflow_actor %}` or by a run name such as "{% data variables.product.prodname_code_quality_short %}: push on main."

assets/images/help/copilot/copilot-sdk/features-hooks-diagram-0.png

@@ -35,7 +35,7 @@ You can enforce these thresholds at the **repository** level, or at the **organi
 
 ## Confirming {% data variables.product.prodname_code_quality_short %} runs successfully on pull requests
 
-Before you add or update a ruleset to include a threshold for {% data variables.product.prodname_code_quality_short %}, confirm that the {% data variables.code-quality.workflow_name_actions %} workflow is running and reporting results back to pull requests. Otherwise, the ruleset could block the merging of **all** pull requests.
+Before you add or update a ruleset to include a threshold for {% data variables.product.prodname_code_quality_short %}, confirm that the {% data variables.product.prodname_code_quality_short %} workflow is running and reporting results back to pull requests. Otherwise, the ruleset could block the merging of **all** pull requests.
 
 1. Open a recent pull request and scroll to the "Checks" summary at the bottom of the pull request.
 1. Confirm that the "{% data variables.code-quality.check_status_name %}" check ran successfully and reported its status.

assets/images/help/copilot/copilot-sdk/setup-choosing-a-setup-path-diagram-0.png

@@ -22,10 +22,6 @@ category:
 
 {% data variables.copilot.copilot_autofix_short %} suggestions are provided for findings where possible.
 
-### Scan information
-
-Each {% data variables.product.prodname_codeql %} analysis will use {% data variables.product.prodname_actions %} minutes and can be seen on the **Actions** tab of the repository. These runs use the workflow name {% data variables.product.prodname_codeql %}, the same name {% data variables.product.prodname_code_scanning %} uses, so you can't reliably tell {% data variables.product.prodname_code_quality_short %} and {% data variables.product.prodname_code_scanning %} runs apart by workflow name. Identify {% data variables.product.prodname_code_quality_short %} runs by their {% data variables.product.prodname_actions %} label instead, for example "Code Quality: push on main"
-
 ### Query lists for supported languages
 
 Each {% data variables.product.prodname_code_quality_short %} rule is written as a query in {% data variables.product.prodname_codeql %} and then run using {% data variables.product.prodname_actions %}.
@@ -43,9 +39,11 @@ For more information about the {% data variables.product.prodname_codeql %} proj
 
 ## Workflow used for code quality analysis
 
-You can see all the workflow runs for {% data variables.product.prodname_code_quality_short %} on the **Actions** tab for your repository. You can identify {% data variables.product.prodname_code_quality_short %} runs by their {% data variables.product.prodname_actions %} label, for example "{% data variables.product.prodname_code_quality_short %}: push on main"
+Each {% data variables.product.prodname_codeql %} analysis will use {% data variables.product.prodname_actions %} minutes. You can see all workflow runs for {% data variables.product.prodname_code_quality_short %} on the repository's **Actions** tab. 
+
+{% data variables.product.prodname_code_quality_short %} and {% data variables.product.prodname_code_scanning %} runs both use the workflow name {% data variables.product.prodname_codeql %}. You can identify {% data variables.product.prodname_code_quality_short %} runs by the actor `{% data variables.code-quality.workflow_actor %}` or by their run name, for example, "{% data variables.product.prodname_code_quality_short %}: push on main."
 
-By default, the {% data variables.code-quality.workflow_name_actions %} workflow runs on standard {% data variables.product.github %} runners but you can configure {% data variables.product.prodname_code_quality_short %} to use runners with a specific label. These may be hosted by {% data variables.product.github %} or self-hosted.
+By default, the {% data variables.product.prodname_code_quality_short %} workflow runs on standard {% data variables.product.github %} runners but you can configure {% data variables.product.prodname_code_quality_short %} to use runners with a specific label. These may be hosted by {% data variables.product.github %} or self-hosted.
 
 If your organization has configured caching of private registries, these will be available for code quality analysis to use to resolve dependencies.