Merge pull request #46293 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/confirm-internal-staff-work-in-docs.yml

@@ -59,7 +59,7 @@ jobs:
               owner: 'github',
               repo: process.env.TEAM_CONTENT_REPO,
               title: `@${context.payload.sender.login} confirm that \#${issueNo} should be in the public github/docs repo`,
-              body: `@${context.payload.sender.login} opened https://github.com/github/docs/issues/${issueNo} publicly in the github/docs repo, instead of the private github/${process.env.TEAM_CONTENT_REPO} repo.\n\n@${context.payload.sender.login}, please confirm that this belongs in the public repo and that no sensitive information was disclosed by commenting below and closing the issue.\n\nIf this was not intentional and sensitive information was shared, please delete https://github.com/github/docs/issues/${issueNo} and notify us in the \#docs-open-source channel.\n\nThanks!`,
+              body: `@${context.payload.sender.login} opened https://github.com/github/docs/issues/${issueNo} publicly in the github/docs repo, instead of the private github/${process.env.TEAM_CONTENT_REPO} repo.\n\n@${context.payload.sender.login}, if this specifically belongs in the public repo, and no sensitive information is disclosed, please ignore this message. Otherwise, please ${context.payload.pull_request ? 'close the pull request and recreate it internally in https://github.com/github/docs-content.' : 'close the issue and reopen it internally in https://github.com/github/docs-content, or transfer it there.'}\n\nIf sensitive information was shared, please close https://github.com/github/docs/issues/${issueNo} and notify us in the \#docs-open-source channel, so we can delete it. Thanks!`,
               labels: ['OS confirmation', 'skip FR board'],
             });
 

assets/images/help/2fa/ghes-3.8-and-higher-2fa-wizard-app-click-code.png

@@ -121,6 +121,20 @@ If the device was already initialized using `ghe-storage-init-backup`, you can r
 
    This will mount the device at `/data/backup` and ensures it's mounted automatically in the future.
 
+{% ifversion backup-service-cluster-ha %}
+{% # Pre-GA, backup-service was only supported on standalone topologies making this step irrelevant %}
+
+1. If using a cluster or high availability (HA) configuration, set the `backup-server` role for the node on which the disk is mounted and apply the configuration.
+
+   Replace `HOSTNAME` with the hostname of the node on which the disk is mounted, as listed in `cluster.conf`.
+
+   ```shell
+   ghe-config cluster.HOSTNAME.backup-server true
+   ghe-config-apply
+   ```
+
+{% endif %}
+
 ### Configuring backup settings
 
 After the backup target is mounted, the Backup Service page will become available in the {% data variables.enterprise.management_console %} in the "Backup" section. {% ifversion ghes > 3.19 %} If your instance is part of a clustered environment, the Backup Service page will be available after `ghe-config-apply`. {% endif %}

content/admin/backing-up-and-restoring-your-instance/configuring-the-backup-service.md

@@ -65,6 +65,9 @@ The models available for {% data variables.product.prodname_copilot_short %} var
 * {% data variables.copilot.copilot_gpt_56_sol %}
 * {% data variables.copilot.copilot_gpt_56_terra %}
 * {% data variables.copilot.copilot_gpt_6_astra %}
+* {% data variables.copilot.copilot_gpt_6_luna %}
+* {% data variables.copilot.copilot_gpt_6_sol %}
+* {% data variables.copilot.copilot_gpt_61_sol %}
 * {% data variables.copilot.copilot_claude_haiku_45 %}
 * {% data variables.copilot.copilot_claude_haiku_55 %}
 * {% data variables.copilot.copilot_claude_opus_48 %}

content/admin/data-residency/github-copilot-with-data-residency.md

@@ -7,7 +7,6 @@ versions:
 redirect_from:
   - /billing/using-the-enhanced-billing-platform-for-enterprises/about-the-billing-cycle
   - /billing/using-the-billing-platform/viewing-your-subscriptions-and-billing-date
-  - /billing/using-the-billing-platform/changing-the-duration-of-your-billing-cycle
   - /billing/using-the-new-billing-platform/viewing-your-subscriptions-and-billing-date
   - /billing/using-the-new-billing-platform/about-the-billing-cycle
   - /billing/managing-your-billing/about-the-billing-cycle
@@ -58,6 +57,10 @@ Changes you make mid-cycle, such as adding or removing users, seats, or resource
 * **Within the same billing account**: No double-billing. Moving users or resources between organizations under the same account is handled automatically.
 * **Between different billing accounts**: Each account is billed according to its own cycle. You may see charges in both accounts if the move overlaps billing periods.
 
+## Changing your billing cycle
+
+In some cases, you can change your billing cycle from monthly to annual, or vice versa. For information about when you can change your billing cycle and how to make the change, see [AUTOTITLE](/billing/how-tos/manage-plan-and-licenses/change-billing-cycle).
+
 ## Where to find usage details for specific products
 
 Find product-specific guidance on how usage is calculated and billed.

content/billing/concepts/billing-cycles.md

@@ -0,0 +1,34 @@
+---
+title: Changing your billing cycle
+shortTitle: Change billing cycle
+intro: 'In some cases, you can change your billing cycle from monthly to annual, or vice versa.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
+  - /articles/monthly-and-yearly-billing
+  - /articles/switching-between-monthly-and-yearly-billing-for-your-personal-account
+  - /articles/switching-between-monthly-and-yearly-billing-for-your-organization
+  - /articles/changing-the-duration-of-your-billing-cycle
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle
+  - /billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle
+  - /billing/using-the-billing-platform/changing-the-duration-of-your-billing-cycle
+versions:
+  fpt: '*'
+  ghec: '*'
+contentType: how-tos
+category:
+  - Manage your plan and licenses
+---
+
+## Who can change their billing cycle
+
+You can change your billing cycle if you have a volume-based plan that supports both monthly and annual billing. The change takes effect at the start of your next billing cycle.
+
+For more information about volume-based plans, see [AUTOTITLE](/billing/concepts/billing-cycles#billing-cycles-for-volume-based-products).
+
+## Changing your billing cycle
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing-plans-two-platforms %}
+
+1. Find the plan you want to update, then select the **Edit** dropdown on the right.
+1. Select the option to change your billing cycle, then follow the prompts.

content/billing/how-tos/manage-plan-and-licenses/change-billing-cycle.md

@@ -22,6 +22,7 @@ versions:
 children:
   - /upgrade-plan
   - /downgrade-plan
+  - /change-billing-cycle
   - /manage-pending-changes
   - /view-enterprise-usage
   - /manage-user-licenses

content/billing/how-tos/manage-plan-and-licenses/index.md

@@ -79,4 +79,11 @@ You do not need to select a model to enable AI Scan.
 
 Organization owners and security managers can review the effective enablement status of AI Scan for pull requests in the "Coverage" view of security overview. See [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/assessing-adoption-code-security).
 
+People with access to security overview can also monitor AI Scan findings across an organization or enterprise:
+
+* The **Prevention** tab on the overview dashboard shows trends in AI Scan findings, how many findings were resolved, and how often developers accepted a {% data variables.copilot.copilot_autofix_short %} suggestion.
+* The **AI Scan** tab in the "Code scanning on pull requests" report shows findings over time, the availability of {% data variables.copilot.copilot_autofix_short %} suggestions, and the outcomes of findings with and without suggestions.
+
+For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/code-scanning-on-pull-requests).
+
 You can use the REST API to manage the organization or repository `ai-scan` setting. See [AUTOTITLE](/rest/code-scanning/code-scanning#get-the-ai-scan-setting-for-an-organization).

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

@@ -37,7 +37,7 @@ With a {% data variables.copilot.copilot_enterprise %} license, you can also ask
 
 {% endif %}
 
-For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/pull-request-alert-metrics).
+For {% data variables.product.prodname_code_scanning %} alerts from {% data variables.product.prodname_codeql %} analysis, you can use security overview to see how {% data variables.product.prodname_codeql %} is performing in pull requests in repositories across your organization, and to identify repositories where you may need to take action. For more information, see [AUTOTITLE](/code-security/concepts/code-scanning/code-scanning-on-pull-requests).
 
 {% data reusables.code-scanning.audit-code-scanning-events %}
 

content/code-security/concepts/code-scanning/code-scanning-alerts.md

@@ -1,7 +1,7 @@
 ---
-title: CodeQL pull request alert metrics
-shortTitle: Pull request alert metrics
-intro: Understand {% data variables.product.prodname_codeql %}'s performance in pull requests across your organizations.
+title: Code scanning on pull requests
+shortTitle: Code scanning on pull requests
+intro: Understand how {% data variables.product.prodname_codeql %}{% ifversion ai-powered-security-detections %} and AI Scan{% endif %} find and help prevent vulnerabilities in pull requests across your organizations.
 permissions: '{% data reusables.permissions.security-overview %}'
 product: '{% data reusables.gated-features.security-overview-fpt-cs-only %}'
 contentType: concepts
@@ -11,14 +11,22 @@ versions:
   ghes: '*'
 category:
   - Secure at scale
+redirect_from:
+  - /code-security/concepts/code-scanning/pull-request-alert-metrics
 ---
 
 ## Overview
 
-The metrics overview for {% data variables.product.prodname_codeql %} pull request alerts on security overview helps you understand how well {% data variables.product.prodname_codeql %} is preventing vulnerabilities in pull requests in your organization or across organizations in your enterprise. You can view the entire dataset or filter for specific criteria, making it easy to identify repositories where you may need to take action to find and reduce security risks.
+The "Code scanning on pull requests" report in security overview helps you understand how well {% data variables.product.prodname_code_scanning %} is preventing vulnerabilities in pull requests in your organization or across organizations in your enterprise. You can view the entire dataset or filter for specific criteria, making it easy to identify repositories where you may need to take action to find and reduce security risks.
+
+{% ifversion ai-powered-security-detections %}
+The report has separate **{% data variables.product.prodname_codeql %}** and **AI Scan** tabs.
+{% endif %}
 
 ## Available metrics
 
+### {% data variables.product.prodname_codeql %} metrics
+
 The overview shows you a summary of how many vulnerabilities prevented by {% data variables.product.prodname_codeql %} have been caught in pull requests. The metrics are only tracked for pull requests that have been merged into the default branches of repositories in your organizations.
 
 You can also find more granular metrics, such as how many alerts were fixed{% ifversion code-scanning-autofix %} with and without {% data variables.copilot.copilot_autofix_short %} suggestions{% endif %}, how many were unresolved and merged, and how many were dismissed as false positive or risk accepted.
@@ -43,6 +51,22 @@ You can also view:
 > [!NOTE] Metrics for {% data variables.copilot.copilot_autofix_short %} are omitted because {% data variables.copilot.copilot_autofix_short %} is available only on {% data variables.product.github %} cloud platforms.
 {% endif %}
 
+{% ifversion ai-powered-security-detections %}
+
+### AI Scan metrics
+
+The **AI Scan** tab shows:
+
+* **Total findings:** The number of AI Scan findings.
+* **Findings with Autofix suggestions:** The number and percentage of findings that had a {% data variables.copilot.copilot_autofix_short %} suggestion.
+* **AI Scan findings in pull requests:** A chart that groups findings over time by **Autofix suggested** and **Autofix not suggested**.
+* **Outcomes of findings with an Autofix suggestion:** The share of findings where a fix was applied or the finding was dismissed.
+* **Outcomes of findings without an Autofix suggestion:** The share of findings where a fix was applied or the finding was dismissed.
+
+The date range and filters that you select apply to all AI Scan metrics displayed in the report.
+
+{% endif %}
+
 ## Visibility
 
 You can see {% data variables.product.prodname_code_scanning %} metrics for a repository if you have:
@@ -53,4 +77,4 @@ You can see {% data variables.product.prodname_code_scanning %} metrics for a re
 
 ## Next steps
 
-To find your pull request alert metrics, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts).
+To view the "Code scanning on pull requests" report, see [AUTOTITLE](/code-security/how-tos/view-and-interpret-data/analyze-organization-data/viewing-metrics-for-pull-request-alerts).