Repo sync

content/apps/using-github-apps/installing-a-github-app-on-your-enterprise.md

@@ -13,9 +13,6 @@ docsTeamMetrics:
   - enterprise-onboarding
 ---
 
-> [!NOTE]
-> Enterprise-installed {% data variables.product.prodname_github_apps %} are in {% data variables.release-phases.public_preview %} and subject to change.
-
 ## About installing {% data variables.product.prodname_github_apps %} on your enterprise
 
 Enterprise-installed {% data variables.product.prodname_github_apps %} are apps that request enterprise-level permissions and can perform operations on your enterprise account. Unlike organization or user installations, they do not have access to any organization or repository permissions—they only manage the enterprise itself.
@@ -54,11 +51,11 @@ The installation token for an enterprise-installed {% data variables.product.pro
 
 ## Current limitations
 
-Enterprise-installed {% data variables.product.prodname_github_apps %} are currently in {% data variables.release-phases.public_preview %} with the following limitations.
+Enterprise-installed {% data variables.product.prodname_github_apps %} have some limitations in what they're able to do.
 
 ### API support
 
-Not all APIs support enterprise-installed {% data variables.product.prodname_github_apps %} yet. As more permissions are built and APIs updated, support will become broader. For more information about the APIs and permissions that support enterprise-installed {% data variables.product.prodname_github_apps %}, see [AUTOTITLE](/rest/authentication/permissions-required-for-github-apps).
+Not all APIs support enterprise-installed {% data variables.product.prodname_github_apps %} yet. As more permissions are built and APIs updated, support will become broader. For more information about the APIs and permissions that support enterprise-installed {% data variables.product.prodname_github_apps %}, see [AUTOTITLE](/rest/authentication/permissions-required-for-github-apps) and [AUTOTITLE](/graphql/guides/managing-enterprise-accounts).
 
 ### Webhook support
 

content/code-security/reference/supply-chain-security/dependabot-options-reference.md

@@ -590,15 +590,15 @@ Package manager | YAML value      | Supported versions |
 | {% ifversion dependabot-nix-support %} |
 | Nix flakes | `nix`            | Not applicable   |
 | {% endif %} |
-| npm            | `npm`            |  v7, v8, v9, v10, v11   |
+| npm            | `npm`            | v7, v8, v9, v10, v11{% ifversion dependabot-npm12-pnpm11-pnpm12-bun14 %}, v12{% endif %} |
 | NuGet          | `nuget`          | <=6.12.0 |
 | {% ifversion dependabot-opentofu-support %} |
 | OpenTofu     | `opentofu`       | Not applicable     |
 | {% endif %} |
 | pip         | `pip`            | 26.1.1             |
 | pip-compile | `pip`            | 7.5.3            |
 | pipenv      | `pip`            | 2024.4.1      |
-| pnpm   | `npm`            | v7, v8, v9, v10   |
+| pnpm        | `npm` | v7, v8, v9, v10{% ifversion dependabot-npm12-pnpm11-pnpm12-bun14 %}, v11, v12{% endif %} |
 | poetry      | `pip`    | v2    |
 | {% ifversion dependabot-pre-commit-support %} |
 | pre-commit | `pre-commit` | Not applicable |

content/code-security/reference/supply-chain-security/dependency-graph-supported-package-ecosystems.md

@@ -61,6 +61,7 @@ In the table below:
 > * If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
 > * {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/workflow-syntax).
 > * {% data reusables.dependabot.dependabot-alert-actions-semver %} For more information, see [AUTOTITLE](/code-security/concepts/supply-chain-security/dependabot-alerts) and [AUTOTITLE](/code-security/concepts/supply-chain-security/dependabot-version-updates).
+{% ifversion dependabot-npm12-pnpm11-pnpm12-bun14 %}> * When pnpm writes `pnpm-lock.yaml` as two YAML documents, the dependency graph does not detect the dependencies in that file. This is the default format for pnpm 12 projects that pin a pnpm version. For more information, see [AUTOTITLE](/code-security/reference/supply-chain-security/supported-ecosystems-and-repositories#pnpm).{% endif %}
 
 {% ifversion dependabot-community-ecosystems %}
 

content/copilot/concepts/billing-and-usage/copilot-usage-metrics/copilot-metrics.md

@@ -52,6 +52,20 @@ The data **does not include** activity from other {% data variables.product.prod
 
 License and seat management data are not included in {% data variables.product.prodname_copilot_short %} usage metrics reports. To view or manage license assignments, use the {% data variables.product.prodname_copilot_short %} user management API, which is the source of truth for license and seat information. See [AUTOTITLE](/rest/copilot/copilot-user-management).
 
+### Troubleshooting missing usage data
+
+Detailed breakdowns depend on client-side telemetry from the IDE or {% data variables.copilot.copilot_cli_short %}. This telemetry provides data about features, languages, models, accepted suggestions, and lines of code. Server-side telemetry can show that a user was active, but it can't observe what happens in the editor.
+
+If client-side telemetry is missing, reports may contain lower numbers or empty breakdowns even when server-side data shows activity. Common causes include:
+
+| Cause | Effect on your reports | What you can check |
+|:--|:--|:--|
+| Telemetry is turned off in the IDE, for example with the `telemetry.telemetryLevel` setting in {% data variables.product.prodname_vscode_shortname %}. | The IDE sends no detailed activity. The user may still be counted as active through server-side telemetry, but feature, language, and lines of code breakdowns are empty. | Confirm that IDE telemetry is enabled for your developers. |
+| A network proxy, firewall, or VPN blocks the {% data variables.product.prodname_copilot_short %} telemetry endpoint. | Same as when telemetry is turned off. | Allow the {% data variables.product.prodname_copilot_short %} client telemetry endpoint. See [AUTOTITLE](/copilot/reference/copilot-allowlist-reference). |
+| The client isn't a supported IDE and doesn't send {% data variables.product.prodname_copilot_short %} telemetry. | The user may be counted as active through server-side telemetry, but the client doesn't appear in `totals_by_ide` or detailed breakdowns. | Use a supported IDE for complete metrics. |
+
+If a gap persists after you check the causes above, contact {% data variables.contact.contact_support %} and include the affected users, IDEs, versions, and dates.
+
 ## Why {% data variables.product.prodname_copilot_short %} usage metrics may differ across API resources
 
 The following API resources expose {% data variables.product.prodname_copilot_short %}-related data, but they are not interchangeable and should not be compared directly. Each API resource is designed for a specific use case and data model, and differences in totals or coverage are expected. Use this table to understand which API resource best fits your reporting needs.
@@ -88,20 +102,48 @@ In short: users must be licensed somewhere in the enterprise to appear in its me
 
 To be included in the {% data variables.product.prodname_copilot_short %} usage metrics, end users must use one of the following IDEs and {% data variables.copilot.copilot_chat_short %} extension versions.
 
+Older versions may not send all the events that usage metrics rely on, or may attribute activity to the wrong IDE. Keep IDEs and {% data variables.product.prodname_copilot_short %} extensions current, and use device management tooling to enforce these minimum versions where possible.
+
 | IDE | Minimum IDE version | Minimum {% data variables.copilot.copilot_chat_short %} extension version |
 |:--|:--|:--|
 | Eclipse | 4.31 | 0.9.3.202507240902 |
 | JetBrains / IntelliJ | 2024.2.6 | 1.5.52-241 |
 | {% data variables.product.prodname_vs %} | 17.14.13 | 18.0.471.29466 |
 | {% data variables.product.prodname_vscode_shortname %} | 1.107.1 | 0.35.3 |
-| Xcode | 13.2.1 | 0.40.0 |
+| Xcode | 14.3.1 | 0.40.0 |
+
+In per-user reports, each `totals_by_ide` entry includes `last_known_ide_version` and `last_known_plugin_version`. Use these fields to identify developers who need to update. See [AUTOTITLE](/copilot/reference/copilot-usage-metrics/copilot-usage-metrics).
+
+### Version requirements for SDK-based agent activity
+
+Some IDEs run {% data variables.product.prodname_copilot_short %} agent sessions through the {% data variables.product.prodname_copilot_short %} SDK. Some versions of these IDEs don't identify themselves when they send agent activity, so that activity is left out of usage metrics. This causes agent interactions and agent lines of code to be undercounted. To include this activity, end users must use one of the following versions or later:
+
+| IDE | Minimum version for SDK-based agent activity | Affected versions |
+|:--|:--|:--|
+| {% data variables.product.prodname_vscode_shortname %} | 1.139.0 | 1.134 through 1.138, when using the agent window |
+| {% data variables.product.prodname_copilot_short %} plugin for JetBrains IDEs | 1.20.0 | 1.15.0 through 1.19.x |
+| {% data variables.product.prodname_vs %} | 18.12 | Insiders (preview) builds before 18.12 |
+
+If you're planning IDE updates, move developers directly to these versions or later. Generally available versions of {% data variables.product.prodname_vs %} aren't affected.
+
+For JetBrains IDEs, avoid {% data variables.product.prodname_copilot_short %} plugin versions 1.15.0 through 1.19.x.
+
+Eclipse and Xcode don't run agent sessions through the {% data variables.product.prodname_copilot_short %} SDK, so they aren't affected.
+
+Missing data can't be backfilled, because activity from affected versions doesn't identify which IDE it came from.
+
+Some of this activity was counted as {% data variables.copilot.copilot_cli_short %} activity instead, which can inflate {% data variables.copilot.copilot_cli_short %} metrics. This clears up as developers update the affected IDEs, but earlier {% data variables.copilot.copilot_cli_short %} metrics can't be corrected. {% data variables.copilot.copilot_cli_short %} users don't need to update.
+
+This issue affects only how activity is attributed in usage metrics. Billing is not affected.
 
 ## Data freshness
 
 The data in the dashboards and API reports is updated on a regular schedule.
 
 You can expect data to be available within **two full days**. This means that data for a given day is processed and made available within two full UTC days after that day closes.
 
+Telemetry that is still being processed can make the most recent days appear incomplete. Wait for the processing window to close before investigating a gap.
+
 ## What does the data measure?
 
 {% data variables.product.prodname_copilot_short %} usage metrics can be grouped into a few main categories: Adoption, engagement, acceptance rate, Lines of Code (LoC), and pull request lifecycle metrics.
@@ -116,6 +158,8 @@ You can expect data to be available within **two full days**. This means that da
 
 **Pull request lifecycle metrics** measure how {% data variables.product.prodname_copilot_short %} activity relates to pull request outcomes and delivery flow. These metrics include pull request creation and merge counts, median time to merge, and review suggestion activity. By comparing overall pull request activity with pull requests created by {% data variables.product.prodname_copilot_short %}, you can evaluate how AI-assisted workflows influence throughput and cycle time at the organization or enterprise level.
 
+Model breakdowns can include models that developers didn't select directly. For example, {% data variables.product.prodname_copilot_short %} can use other models for Auto model selection or for background tasks.
+
 ### Understanding adoption cohorts
 
 Rather than measuring adoption as a single active-user count, {% data variables.product.prodname_copilot_short %} groups users into **adoption cohorts** based on how they engage with {% data variables.product.prodname_copilot_short %}, not just whether they engage at all. A flat active-user count treats someone who occasionally accepts a code completion the same as someone who orchestrates multiple agent-driven workflows throughout the day. Cohorting separates these two users, so you can see whether your organization's usage is deepening over time rather than plateauing at initial trial.

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/enable-copilot-cloud-agent.md

@@ -26,7 +26,8 @@ docsTeamMetrics:
 
 ## Prerequisites
 
-You may want to run a trial before enabling {% data variables.copilot.copilot_cloud_agent %} for the enterprise. See [AUTOTITLE](/copilot/tutorials/cloud-agent/pilot-cloud-agent).
+- Optionally, run a trial. See [AUTOTITLE](/copilot/tutorials/cloud-agent/pilot-cloud-agent).
+- Review enterprise policies, repository protections, and runner settings with organization owners and repository administrators. See [AUTOTITLE](/copilot/tutorials/cloud-agent/build-guardrails).
 
 ## Enabling {% data variables.copilot.copilot_cloud_agent %}
 

content/copilot/how-tos/copilot-cli/administer-copilot-cli-for-your-enterprise.md

@@ -76,6 +76,10 @@ All other controls do **not** affect {% data variables.copilot.copilot_cli_short
 
 * **IDE-specific policies**: Policies configured for specific IDEs or editor extensions
 
+## Applying guardrails so teams follow organizational policies
+
+You can apply guardrails to keep developer's use within organizational policies. First, work with platform and security teams to decide which {% data variables.copilot.copilot_cli_short %} actions need review, ultimately agreeing on what usage information to log. Prefer collecting only the minimum data needed (for example, metadata rather than full prompt contents), and redact or mask secrets and personal data before writing any logs. If teams configure repository-scoped hooks to log prompts and tool use, ensure log access is restricted to authorized personnel and follow your organization's retention and deletion requirements so sensitive data is not stored longer than necessary. These hooks can also block selected command patterns. See [AUTOTITLE](/copilot/tutorials/copilot-cli-hooks).
+
 ## Why can't my developers access {% data variables.copilot.copilot_cli_short %}?
 
 If you expect a user to have access to {% data variables.copilot.copilot_cli_short %} and they don't:

content/copilot/how-tos/copilot-cli/set-up-copilot-cli/authenticate-copilot-cli.md

@@ -218,7 +218,7 @@ To revoke the OAuth app authorization on {% data variables.product.github %} and
    1. In the upper-right corner of any page on {% data variables.product.prodname_dotcom %}, click your profile picture.
    1. Click **Settings**.
 1. In the left sidebar, click **Applications**.
-1. Under **Authorized OAuth Apps**, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to **GitHub CLI** to expand the menu and select **Revoke**.
+1. Under **Authorized OAuth Apps**, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to **{% data variables.copilot.copilot_cli %}** to expand the menu and select **Revoke**.
 
 ## Next steps
 

content/copilot/reference/copilot-usage-metrics/lines-of-code-metrics.md

@@ -34,6 +34,7 @@ LoC metrics may vary across IDEs and versions. Keep the following considerations
 
 * **Coverage:** Not all IDEs and users will emit LoC telemetry until they upgrade to the required versions. Reports include the `last_known_ide_version` and `last_known_plugin_version` fields so you can monitor coverage across your enterprise.
 * **Stability:** As {% data variables.product.prodname_copilot_short %} evolves, telemetry definitions may change. Expect small shifts in data as accuracy improves over time.
+* **Comparison with editor views:** LoC metrics only include changes that the client reports through telemetry. They may not match line counts in an editor diff view.
 
 ## Version requirements
 
@@ -51,7 +52,7 @@ LoC metrics require specific minimum versions of IDEs and {% data variables.prod
 | | <ul><li>`chat_panel` (Ask, Edit, Plan, Agent)</li></ul> | 1.102.0 | 0.29.0 |
 | | <ul><li>`chat_inline`</li></ul> | 1.103.2 | 0.30.3 |
 | | <ul><li>`agent_edit`</li></ul> | 1.103.0 | 0.30.0 |
-| XCode | <ul><li>`code_completion`</li></ul> | 14.3.1 | 0.40.0 |
+| Xcode | <ul><li>`code_completion`</li></ul> | 14.3.1 | 0.40.0 |
 | | <ul><li>`chat_panel` (Ask, Edit, Plan, Agent)</li></ul> | 15.0 | 0.43.0 |
 | | <ul><li>`agent_edit`</li></ul> | 15.2 | 0.41.0 |