Merge pull request #45259 from github/repo-sync

Repo sync

Author: docs-bot

content/billing/concepts/enterprise-billing/billing-for-enterprises.md

@@ -1,6 +1,6 @@
 ---
 title: Billing for GitHub Enterprise
-intro: 'Learn how your bill is calculated based on how many {% data variables.product.prodname_enterprise %} licenses you use.'
+intro: 'Understand what makes up your enterprise bill so you can better forecast and manage costs.'
 redirect_from:
   - /admin/overview/managing-billing-for-your-enterprise
   - /enterprise/admin/installation/managing-billing-for-github-enterprise
@@ -12,6 +12,7 @@ redirect_from:
   - /billing/using-the-billing-platform/about-billing-for-your-enterprise
   - /billing/using-the-new-billing-platform/about-billing-for-your-enterprise
   - /billing/managing-your-billing/about-billing-for-your-enterprise
+  - /enterprise-onboarding/getting-started-with-your-enterprise/about-enterprise-billing
 versions:
   fpt: '*'
   ghec: '*'
@@ -20,42 +21,55 @@ shortTitle: Billing for enterprises
 contentType: concepts
 category:
   - Manage enterprise licenses
+docsTeamMetrics:
+  - enterprise-onboarding
 ---
 
-## {% data variables.product.prodname_enterprise %} plan costs
+## What's included in my {% data variables.product.prodname_ghe_cloud %} bill?
 
-Each member of your enterprise uses a license (previously known as a seat). The bill for your {% data variables.product.prodname_enterprise %} plan is based on the number of licenses consumed by your enterprise.
+Each month, you're billed for:
 
-If you have an enterprise account on {% data variables.product.prodname_ghe_cloud %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns. Enterprise owners and billing managers can access and manage billing for the enterprise. For more information, see [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles).
+* The number of {% data variables.product.prodname_enterprise %} licenses you use, determined by the number of unique users in your enterprise
+* Any usage of features like {% data variables.product.prodname_actions %} or {% data variables.product.prodname_github_codespaces %}, beyond the allowances included in your {% data variables.product.prodname_enterprise %} plan
+* Any extra features you purchase, such as {% data variables.product.prodname_copilot %} or {% data variables.product.prodname_AS %} licenses
 
-> [!TIP]
-> {% ifversion fpt or ghec %}
-> If you use {% data variables.product.prodname_ghe_cloud %} with an individual organization and do not yet have an enterprise account, you can create an enterprise account and add your organization. For more information, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-your-enterprise-account/creating-an-enterprise-account).
-> {% elsif ghes %}
-> {% data reusables.billing.ghes-with-no-enterprise-account %}
-> {% endif %}
+For prices and monthly allowances, see {% data variables.product.pricing_link %}.
 
-To learn which people consume a license in your enterprise, see [AUTOTITLE](/billing/reference/github-license-users).
+## What's included in my {% data variables.product.prodname_ghe_server %} bill?
+
+Your bill includes the cost of {% data variables.product.prodname_enterprise %} licenses used, as well as any extra features you purchase, such as {% data variables.product.prodname_copilot %} or {% data variables.product.prodname_AS %} licenses.
+
+>[!TIP] {% data variables.product.prodname_ghe_server %} customers with no enterprise account on {% data variables.product.prodname_dotcom_the_website %} can view invoices and payment history on the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/login).
+
+## Paying for your enterprise
+
+For the available payment methods for your enterprise, see [AUTOTITLE](/billing/reference/supported-payment-methods).
 
 ## Invoiced customers
 
+If you created your enterprise account with help from {% data variables.product.company_short %}'s Sales team, you may have agreed to pay by invoice instead.
+
 For invoiced customers, each invoice includes a single bill that covers the cost of {% data variables.product.prodname_enterprise %} licenses used, as well as your use of paid services. For example, in addition to your usage for {% data variables.product.prodname_enterprise %}, you may also use {% data variables.product.prodname_GH_secret_protection %}.
 
-## Billing models for {% data variables.product.prodname_enterprise %} licenses
+## License costs
+
+The following sections describe the {% data variables.product.prodname_enterprise %} license component of your bill specifically.
+
+Each member of your enterprise uses a license (previously known as a seat). The license portion of your bill is based on the number of licenses consumed by your enterprise. To learn which people consume a license in your enterprise, see [AUTOTITLE](/billing/reference/github-license-users).
+
+### Billing models for {% data variables.product.prodname_enterprise %} licenses
 
 There are two billing models for {% data variables.product.prodname_enterprise %} licenses: **usage-based** and **volume**.
 
 {% data reusables.billing.do-i-have-usage-based %}
 
-## License usage across deployments
+### License usage across deployments
 
 {% data reusables.enterprise-licensing.unique-user-licensing-model %}
 
 To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. See [AUTOTITLE](/billing/concepts/enterprise-billing/combined-enterprise-use).
 
 ## Further reading
 
-* [AUTOTITLE](/admin/concepts/enterprise-fundamentals/enterprise-accounts)
 * [AUTOTITLE](/billing/reference/github-license-users)
 * [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/view-enterprise-usage)
-* [AUTOTITLE](/enterprise-cloud@latest/billing/how-tos/set-up-payment/manage-enterprise-invoice){% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}

content/billing/concepts/product-billing/github-code-quality.md

@@ -13,14 +13,33 @@ category:
 ## How {% data variables.product.prodname_code_quality %} billing is measured
 
 Use of {% data variables.product.prodname_code_quality_short %} incurs three types of costs for an organization:
-* **{% data variables.product.prodname_actions %} minutes** — {% 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. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-actions).
-* **{% 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 %} 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).
-* **Active committers** — {% data variables.product.prodname_code_quality %} is a standalone product with its own license: it uses **one {% data variables.product.prodname_code_quality %} license per active committer**, and does not consume {% data variables.product.prodname_GH_advanced_security %} or any other product's licenses. Your license usage is calculated based on the number of unique, active committers to repositories with {% data variables.product.prodname_code_quality_short %} enabled. {% data variables.product.prodname_github_app %} bots are ignored. For information about differences between bot and machine accounts, see [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps#machine-vs-bot-accounts).
+
+* [{% data variables.product.prodname_actions %} minutes](#github-actions-minutes)
+* [{% data variables.product.prodname_ai_credits %}](#github-ai-credits)
+* [Active and unique committers](#active-and-unique-committers)
+
+### {% data variables.product.prodname_actions %} minutes
+
+{% 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).
+
+### {% 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 %} 
+
+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).
 
 ### Active and unique committers
 
-Each **active committer** to at least one repository with {% data variables.product.prodname_code_quality_short %} enabled uses **one {% data variables.product.prodname_code_quality %} license**. A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored.
+{% data variables.product.prodname_code_quality_short %} is a standalone product with its own license, and does not consume {% data variables.product.prodname_GH_advanced_security %} or any other product's licenses. {% data variables.product.prodname_github_app %} bots are ignored. For information about differences between bot and machine accounts, see [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps#machine-vs-bot-accounts).
+
+* Your license usage is calculated based on the number of unique, active committers to repositories with {% data variables.product.prodname_code_quality_short %} enabled. 
+* Each **active committer** uses **one {% data variables.product.prodname_code_quality_short %} license**. 
+* A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored.
+* A committer is considered active if one of their commits has been pushed to the repository within the last 90 days, regardless of when it was originally authored.
 
+To understand your license usage, and which licenses you can free up, it helps to distinguish between active and unique committers. You can see the number of licenses you're using on the **Licensing** page for your organization or enterprise, shown as **"Consumed licenses"**:
 * **Active committers** are committers who contributed to at least one repository and have a {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} license with your organization or enterprise. This includes members, enterprise-managed users, external collaborators, and people with a pending invitation to join your organization or enterprise.
 * **Unique committers** is the number of active committers who contributed only to one repository, or only to repositories in one organization. You can free up this number of licenses by disabling {% data variables.product.prodname_code_quality_short %} for that repository or organization.
 

content/billing/get-started/index.md

@@ -11,7 +11,6 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '*'
 children:
   - /how-billing-works
   - /introduction-to-billing

content/billing/tutorials/index.md

@@ -5,7 +5,6 @@ intro: Build skills and knowledge about billing through examples and hands-on ac
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '*'
 children:
   - /automate-usage-reporting
   - /soft-budgets

content/code-security/how-tos/maintain-quality-code/roll-out-at-scale.md

@@ -59,7 +59,6 @@ A few things to know about how organization-level enablement behaves, so you can
 
 * Your **Repository access** choice applies to **both existing and future repositories**, so repositories created later inherit your choice automatically. This is true for **All repositories**, **Matching a filter**, and **No repositories**.
 * Turn on **Enforce access** for a guaranteed baseline that repository administrators can't override. Leave it off, or choose **Let repositories decide**, to let teams opt in on their own timeline.
-* Enabling {% data variables.product.prodname_code_quality_short %} does **not** automatically turn on **code coverage**. Coverage is opt-in per repository. It starts reporting only after someone adds a workflow that uploads coverage data, so teams can adopt {% data variables.product.prodname_code_quality_short %} first and add coverage later. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/set-up-code-coverage).
 
 For the full list of access options and how enforcement works, see [AUTOTITLE](/code-security/concepts/code-quality/enablement-at-scale#organization-level-repository-access).
 
@@ -69,6 +68,14 @@ For most rollouts, enabling through the UI is the best starting point: it lets y
 
 If you need automation around your rollout, you can fetch {% data variables.product.prodname_code_quality_short %} findings through the REST API, which is useful for reporting on progress as you expand. You can also enable {% data variables.product.prodname_code_quality_short %} on repositories through the REST API, so you can script enablement across your organization instead of enabling each repository in the UI. See [AUTOTITLE](/rest/code-quality/code-quality).
 
+## Set up code coverage
+
+**Add code coverage once your thresholds are tuned.** Code coverage is separate from the quality thresholds you rolled out in the previous steps, so you can turn it on whenever it suits your teams, or skip it entirely if you don't want it.
+
+Enabling {% data variables.product.prodname_code_quality_short %} does not automatically turn on code coverage. Coverage is opt-in per repository, and it starts reporting only after a workflow that uploads coverage data is added to the repository. This means teams can adopt {% data variables.product.prodname_code_quality_short %} first and add coverage later.
+
+To set up coverage for a repository, see [AUTOTITLE](/code-security/how-tos/maintain-quality-code/set-up-code-coverage).
+
 ## Next steps
 
-* **Assess health across your organization.** See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/explore-code-quality).
+Now that you've rolled out {% data variables.product.prodname_code_quality_short %} across your organization, you can assess the health of your repositories at a glance and decide where to focus. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/explore-code-quality).

content/code-security/how-tos/maintain-quality-code/set-pr-thresholds.md

@@ -23,7 +23,7 @@ You can set thresholds for:
 * **{% data variables.product.prodname_codeql %} findings**, by the lowest severity of results you require to be resolved.
 * **Code coverage**, by the minimum percentage of code that must be covered by tests.
 
-You can enforce these thresholds at the **repository** level, or at the **organization** level to apply the same standard across many repositories at once. Choose the organization level when you want a consistent quality bar across teams, and the repository level when a single project needs its own standard. {% data variables.product.prodname_code_quality_short %} AI detections cannot be set as a threshold.
+You can enforce these thresholds at the **repository** level, or at the **organization** level to apply the same standard across many repositories at once. Choose the organization level when you want a consistent quality bar across teams, and the repository level when a single project needs its own standard. {% data variables.product.prodname_code_quality_short %} {% data variables.code-quality.recent_suggestions %} cannot be set as a threshold.
 
 ## Prerequisites
 

content/code-security/how-tos/maintain-quality-code/view-and-manage-cost.md

@@ -21,7 +21,7 @@ Knowing what {% data variables.product.prodname_code_quality_short %} costs, and
 
 * **License usage**, based on the number of unique, active committers to repositories where {% data variables.product.prodname_code_quality_short %} is enabled.
 * **{% data variables.product.prodname_actions %} minutes**, consumed each time a scan runs (unless you use self-hosted runners).
-* **{% data variables.product.prodname_ai_credits %}**, consumed by {% data variables.product.prodname_code_quality_short %}'s AI features: the fixes it generates for findings, and the AI detections scans if you turn that page on.
+* **{% data variables.product.prodname_ai_credits %}**, consumed by {% data variables.product.prodname_code_quality_short %}'s AI features: the fixes it generates for findings, and the scans on the **{% data variables.code-quality.recent_suggestions %}** page if you turn it on.
 
 For exactly how each cost is measured, see [AUTOTITLE](/billing/concepts/product-billing/github-code-quality?utm_campaign=code-quality-ga-july-2026&utm_medium=docs&utm_source=docs-view-manage-cost-billing).
 
@@ -53,9 +53,7 @@ You have several levers to keep spend in check. In rough order of impact:
 * **Enable selectively.** Turn {% data variables.product.prodname_code_quality_short %} on where it adds value rather than across every repository at once. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/enable-code-quality).
 * **Disable low-value repositories.** Disabling {% data variables.product.prodname_code_quality_short %} on a repository frees the licenses for committers unique to it, and stops its scans and AI usage. See [AUTOTITLE](/code-security/how-tos/maintain-quality-code/disable-code-quality).
 * **Set a budget.** A budget for {% data variables.product.prodname_code_quality_short %} stops your spending automatically once you hit your limit, because the hard stop is mandatory (see below).
-* **Keep the AI detections page off.** This page is **off by default** and stays in {% data variables.release-phases.public_preview %}, so it only draws down {% data variables.product.prodname_ai_credits_short %} if you turn it on. Repositories that enabled it during the preview keep it on, so turn it off there if you don't want the usage.
-
-<!-- VERIFY before GA: exact path to turn off the AI detections page for a repo that enabled it during preview. (Default-off-at-GA confirmed in github/security-products#2357.) -->
+* **Keep the {% data variables.code-quality.recent_suggestions %} page off.** This page is **off by default** and stays in {% data variables.release-phases.public_preview %}, so it only draws down {% data variables.product.prodname_ai_credits_short %} if you turn it on. Repositories that enabled it during the preview keep it on. To turn it off for a repository, disable **{% data variables.code-quality.recent_suggestions %}** on the repository's **{% data variables.code-quality.code_quality_ui %}** settings page.
 
 ### Setting a budget