Repo sync

content/admin/data-residency/network-details-for-ghecom.md

@@ -111,8 +111,8 @@ Most {% data variables.product.prodname_copilot %} services require access to yo
 
 | Runner type | Supported regions |
 | ----------- | ----------------- |
-| x64 | `francecentral`, `swedencentral`, `germanywestcentral`, `northeurope` |
-| arm64 | `francecentral`, `northeurope`, `germanywestcentral` |
+| x64 | `francecentral`, `swedencentral` |
+| arm64 | `francecentral` |
 | GPU | `italynorth`, `swedencentral` |
 
 ### Supported regions in Australia

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

@@ -77,4 +77,6 @@ You do not need to select a model to enable AI Scan.
 * **Organization**: The **AI Scan** setting under "Code scanning" enables AI Scan for eligible repositories in the organization where {% data variables.product.prodname_code_scanning %} is enabled. See [AUTOTITLE](/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/configure-global-settings#enabling-ai-scan).
 * **Repository**: For an organization-owned repository, the **AI Scan for pull requests** toggle under "Code scanning" lets repository administrators opt out when AI Scan is enabled for the organization. For an eligible public repository owned by a personal account, the toggle enables or disables AI Scan directly.
 
+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).
+
 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/how-tos/view-and-interpret-data/analyze-organization-data/export-data.md

@@ -19,6 +19,10 @@ category:
 
 The CSV file you download will contain data corresponding to the filters you have applied to security overview. For example, if you add the filter `dependabot-alerts:enabled`, your file will only contain data for repositories that have enabled {% data variables.product.prodname_dependabot_alerts %}.
 
+{% ifversion ai-powered-security-detections %}
+CSV files exported from the "Coverage" view include a `Code Scanning AI Scan for pull requests` column. The value for each repository is `enabled` or `not-enabled`.
+{% endif %}
+
 > [!NOTE]
 > In the "Teams" column of the CSV file, each repository will list a maximum of 20 teams with write access to that repository. If more than 20 teams have write access to a repository, the data will be truncated.
 

content/code-security/reference/security-at-scale/overview-dashboard-filters.md

@@ -117,6 +117,9 @@ You can limit the data to repositories owned by a single organization in your en
 | Qualifier | Description |
 | -------- | -------- |
 | `code-scanning-default-setup`| Display data for repositories where {% data variables.product.prodname_code_scanning %} is enabled or not enabled using {% data variables.product.prodname_codeql %} default setup. |
+| {% ifversion ai-powered-security-detections %} |
+| `code-scanning-ai-scan-pr-scan` | Display data for repositories where AI Scan for pull requests is effectively enabled or not enabled. Use `code-scanning-ai-scan-pr-scan:enabled` to display enabled repositories, or `code-scanning-ai-scan-pr-scan:not-enabled` to display repositories where the feature is not enabled. |
+| {% endif %} |
 | `code-scanning-pull-request-alerts`| Display data for repositories where {% data variables.product.prodname_code_scanning %} is enabled or not enabled to run on pull requests. |
 | `dependabot-security-updates` | Display data for repositories where {% data variables.product.prodname_dependabot_security_updates %} is enabled or not enabled.  |
 | `secret-scanning-push-protection` | Display data for repositories where push protection for {% data variables.product.prodname_secret_scanning %} is enabled or not enabled. |

content/copilot/how-tos/copilot-cli/use-copilot-cli/work-with-multiple-sessions.md

@@ -43,7 +43,7 @@ The sidebar is a panel that opens alongside your current chat. Because it sits b
 
 ### Opening and closing the sidebar
 
-From your conversation, while there is nothing in the prompt input field, press <kbd>←</kbd> to open the sidebar and move focus into it. Press <kbd>→</kbd> to move focus back to the conversation, and again to close the sidebar. If you prefer Vim-style keys, <kbd>h</kbd> and <kbd>l</kbd> work the same way while the sidebar has focus.
+From your conversation, while there is nothing in the prompt input field, press <kbd>←</kbd> to open the sidebar, then press <kbd>←</kbd> again to move focus into it. Press <kbd>→</kbd> to move focus back to the conversation, and again to close the sidebar. If you prefer Vim-style keys, <kbd>l</kbd> works the same as <kbd>→</kbd> while the sidebar has focus.
 
 ### Moving between sessions
 
@@ -167,9 +167,9 @@ Sessions can also run **remotely**. When you delegate a task with [`/delegate`](
 
 ### Stopping a session
 
-To stop the session you are currently working in, use the `/exit` slash command. Alternatively, you can stop a session from the sidebar by highlighting it and pressing <kbd>x</kbd>. This stops the session and removes it from the sidebar until you resume it.
+To stop the session you are currently working in without deleting it, use the `/exit` slash command. The session is saved and you can resume it later.
 
-Stopping a session doesn't delete it. The session is saved and you can resume it later.
+Alternatively, you can permanently delete a session from the sidebar by highlighting it and pressing <kbd>x</kbd> twice. {% data reusables.copilot.close-session %}
 
 You don't have to stop sessions. Leaving them running lets you switch back instantly with their full context. But you might stop one to halt work you no longer want: for example, a session running in autopilot mode, or a session running a prompt that you scheduled with `/every` or `/after`. You might also choose to stop a session to free up memory, or just to reduce clutter in the sidebar.
 
@@ -190,7 +190,7 @@ You can manage sessions with slash commands from inside any session:
 | `/session checkpoints [N]` | Show the session's checkpoints. |
 | `/session cleanup`, `/session prune` | Housekeeping for old or stale session data. |
 | `/session delete [ID]`, `/session delete-all` | Delete a session, or all of them. |
-| `/exit`, `/quit` | Close the current session. If others are open, the newest remaining one comes to the foreground. The CLI quits only when you close the last session. |
+| `/exit`, `/quit` | Close the current session. If others are open, the nearest remaining one in the sidebar order comes to the foreground. The CLI quits only when you close the last session. |
 
 ## Customizing the sidebar
 

content/site-policy/github-terms/github-marketplace-developer-agreement.md

@@ -62,7 +62,7 @@ Notwithstanding any of the requirements set forth in Section 2 (Purpose and Lice
 
 **3.2**	In order to use and access a GitHub API, Developer must obtain a Token by becoming a subscriber. Developer may not share its Token with any third party, shall keep its Token and all login information secure, and shall use the Token as Developer’s sole means of accessing a GitHub API.
 
-**3.3**	Developer will not engage in any activity with Marketplace, including attempting to distribute any Developer Product, that violates GitHub's Terms of Service including [Acceptable Use Policies](https://docs.github.com/en/site-policy/acceptable-use-policies/github-acceptable-use-policies). Additionally, Developer will not attempt to distribute any Developer Product that:
+**3.3**	Developer will not engage in any activity with Marketplace, including attempting to distribute any Developer Product, that violates GitHub's Terms of Service including [AUTOTITLE](/site-policy/acceptable-use-policies/github-acceptable-use-policies). Additionally, Developer will not attempt to distribute any Developer Product that:
 
 * (i) Contains or installs any active malware or exploits, or uses our platform for exploit delivery (such as part of a command and control system);
 * (ii) Enables the unauthorized download of streaming content or media; or
@@ -102,7 +102,7 @@ If GitHub is notified by you or otherwise becomes aware and determines, in its s
 * (iii) is deemed by GitHub to add undue risk to Marketplace End Users’ data or impair the user experience of Marketplace or GitHub; or
 * (iv) is subject to End User complaints in regards to your breach of your EULA,
 
-GitHub may: suspend the transfer of Personal Data to your Developer Product; prohibit the collection and processing of Personal Data via your Developer Product; remove the Listing from Marketplace; flag, filter, or modify related materials (including but not limited to descriptions, screenshots, or metadata); or reclassify the Listing at its sole discretion. If GitHub takes any of these actions on your Listing, you may appeal GitHub's action through the [GitHub Appeal and Reinstatement Process](https://docs.github.com/en/site-policy/acceptable-use-policies/github-appeal-and-reinstatement)
+GitHub may: suspend the transfer of Personal Data to your Developer Product; prohibit the collection and processing of Personal Data via your Developer Product; remove the Listing from Marketplace; flag, filter, or modify related materials (including but not limited to descriptions, screenshots, or metadata); or reclassify the Listing at its sole discretion. If GitHub takes any of these actions on your Listing, you may appeal GitHub's action through the [GitHub Appeal and Reinstatement Process](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement)
 
 **4.3**	Developer Product Updates. From time to time, GitHub may check for available updates to any Listing, including but not limited to bug fixes or enhanced functionality. If you update your Listing to Marketplace, you agree that such update will be automatically requested, downloaded, and installed without further notice to you. GitHub makes no guarantees regarding the timing of such updates. Updates to a Listing are subject to the same terms and conditions as the Listing.
 
@@ -195,7 +195,7 @@ In order to operate and improve Marketplace, GitHub may collect Usage Data from
 
 ## 19. PRE-RELEASE ACCESS
 
-If you have a Listing on a portion of Marketplace that is in a beta or similar pre-release status, your use of that portion is governed by GitHub’s [Pre-release License Terms](https://docs.github.com/en/site-policy/github-terms/github-pre-release-license-terms).
+If you have a Listing on a portion of Marketplace that is in a beta or similar pre-release status, your use of that portion is governed by GitHub’s [Pre-release License Terms](/site-policy/github-terms/github-pre-release-license-terms).
 
 # Addendum 1: Data Protection Addendum
 

content/site-policy/privacy-policies/github-general-privacy-statement.md

@@ -97,10 +97,10 @@ We may share Personal Data with the following recipients:
 * Abuse and Fraud Prevention Entities: We may disclose Personal Data based on a good faith belief it is needed to prevent fraud, abuse, or attacks on our Services, or to protect the safety of GitHub and our users.
 * Affiliates: Personal Data may be shared with GitHub affiliates, including Microsoft, to facilitate customer service, marketing and advertising, order fulfillment, billing, technical support, legal and compliance obligations, product development and improvement (including training and improving artificial intelligence and machine learning technologies), and for other purposes described in their respective privacy statements. When we share data with affiliates, they will process it in accordance with applicable law and their privacy commitments.
 * GitHub Organization Accounts: If an organization adds you to their GitHub account, we might share Personal Data with that organization to fulfill the commercial relationship. In such a case, your use of the Services is protected by a data protection agreement and terms between your organization and GitHub
-* Competent Authorities: We may disclose Personal Data to authorized law enforcement, regulators, courts, or other public authorities in response to lawful requests or to protect our rights and safety. Please refer to our [Guidelines for Legal Requests of User Data](https://docs.github.com/en/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data) for more information.
+* Competent Authorities: We may disclose Personal Data to authorized law enforcement, regulators, courts, or other public authorities in response to lawful requests or to protect our rights and safety. Please refer to our [AUTOTITLE](/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data) for more information.
 * Corporate Transaction Entities: we might disclose Personal Data within the limits of the law and in accordance with this Privacy Statement for strategic business transactions such as sales or a merger.
 * Partners and Resellers: We cooperate with third-parties that offer sales, consulting, support, and technical services for our Services. We may share your data with these partners and resellers where allowed, and with your consent when required.
-* Subprocessors and Service Providers: We may use vendors to provide services on our behalf, including hosting, marketing, advertising, social, analytics, support ticketing, credit card processing, or security services. They are bound by contractual obligations to ensure the security, privacy, and confidentiality of your information. Please visit <https://docs.github.com/en/site-policy/privacy-policies/github-subprocessors> to see our list of Subprocessors.
+* Subprocessors and Service Providers: We may use vendors to provide services on our behalf, including hosting, marketing, advertising, social, analytics, support ticketing, credit card processing, or security services. They are bound by contractual obligations to ensure the security, privacy, and confidentiality of your information. Please visit [AUTOTITLE](/site-policy/privacy-policies/github-subprocessors) to see our list of Subprocessors.
 * Visual Studio Code (GitHub Codespaces): GitHub Codespaces and github.dev offer Visual Studio Code in a web browser, where some telemetry is collected by default. Details on telemetry collection are on the [VS Code website](https://code.visualstudio.com/docs/configure/telemetry). To opt out, go to File > Preferences > Settings in the top left menu of VS Code. Opting out will sync this preference across all future web sessions in GitHub Codespaces and github.dev.
 * Other Third-party Applications: Upon your instruction, we may share Personal Data with third-party applications available on our Marketplace. You are responsible for the data you instruct us to share with these applications.
 * Other Users and the Public: Depending on your account settings, we may share Personal Data with other users of the Services and the public. You control what information is made public. To adjust your settings, visit User Settings in your profile. Please be aware that any information you share in a collaborative context may become publicly accessible.

data/reusables/code-scanning/using-security-overview-coverage.md

@@ -1,4 +1,7 @@
 1. Use options in the page summary to filter results to show the repositories you want to assess. The list of repositories and metrics displayed on the page automatically update to match your current selection. For more information on filtering, see [AUTOTITLE](/code-security/how-tos/manage-security-alerts/remediate-alerts-at-scale/filtering-alerts-in-security-overview).
+{% ifversion ai-powered-security-detections %}
+   For **AI Scan for pull requests**, the summary shows the number of repositories where the feature is enabled or not enabled, and the repository list shows each repository's status. An `enabled` status reflects effective enablement after enterprise policy, organization configuration, prerequisites, and any repository opt-out are applied. A `not enabled` status can include repositories that are ineligible for AI Scan, and security overview does not distinguish the reason why the feature is not enabled.
+{% endif %}
     * Use the **Teams** dropdown to show information only for the repositories owned by one or more teams. For more information, see [AUTOTITLE](/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/managing-team-access-to-an-organization-repository).
     * Click **NUMBER enabled** or **NUMBER not enabled** in the header for any feature to show only the repositories with that feature enabled or not enabled.
     * At the top of the list of repositories, click **NUMBER Archived** to show only repositories that are archived.

data/reusables/copilot/close-session.md

@@ -1 +1 @@
-Sessions that are running are ended, saved, and removed from the sidebar. Sessions that are not running are simply removed from the sidebar. Sessions you remove in this way are not displayed in the sidebar in future sessions unless you resume the session—for example, from the <code>>/resume</code> session picker.
+The session is permanently deleted, whether or not it was still running. You won't be able to resume a session that's been removed this way.

src/github-apps/data/fpt-2022-11-28/fine-grained-pat-permissions.json

@@ -8715,6 +8715,15 @@
         "additional-permissions": false,
         "access": "write"
       },
+      {
+        "category": "pulls",
+        "slug": "rerequest-reviewers-for-a-pull-request",
+        "subcategory": "review-requests",
+        "verb": "post",
+        "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers/rerequest",
+        "additional-permissions": false,
+        "access": "write"
+      },
       {
         "category": "pulls",
         "slug": "list-reviews-for-a-pull-request",

src/github-apps/data/fpt-2022-11-28/fine-grained-pat.json

@@ -4742,6 +4742,12 @@
       "verb": "delete",
       "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers"
     },
+    {
+      "slug": "rerequest-reviewers-for-a-pull-request",
+      "subcategory": "review-requests",
+      "verb": "post",
+      "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers/rerequest"
+    },
     {
       "slug": "list-reviews-for-a-pull-request",
       "subcategory": "reviews",

src/github-apps/data/fpt-2022-11-28/server-to-server-permissions.json

@@ -10977,6 +10977,17 @@
         "server-to-server": true,
         "additional-permissions": false
       },
+      {
+        "category": "pulls",
+        "slug": "rerequest-reviewers-for-a-pull-request",
+        "subcategory": "review-requests",
+        "verb": "post",
+        "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers/rerequest",
+        "access": "write",
+        "user-to-server": true,
+        "server-to-server": true,
+        "additional-permissions": false
+      },
       {
         "category": "pulls",
         "slug": "list-reviews-for-a-pull-request",

src/github-apps/data/fpt-2022-11-28/server-to-server-rest.json

@@ -4942,6 +4942,12 @@
       "verb": "delete",
       "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers"
     },
+    {
+      "slug": "rerequest-reviewers-for-a-pull-request",
+      "subcategory": "review-requests",
+      "verb": "post",
+      "requestPath": "/repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers/rerequest"
+    },
     {
       "slug": "list-reviews-for-a-pull-request",
       "subcategory": "reviews",