Merge pull request #41251 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/monitoring-and-managing-your-instance/configuring-high-availability/answers-to-common-questions-about-high-availability-replicas.md

@@ -1,5 +1,5 @@
 ---
-title: Answers to common questions about high-availability replicas
+title: Answers to common questions about high availability replicas
 intro: 'Find information about high availability replica types, communication patterns, maintenance operations, and how to choose the right replica for your deployment.'
 versions:
   ghes: '*'

content/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-user-access-token-for-a-github-app.md

@@ -60,14 +60,11 @@ If your app runs in the browser, you should use the web application flow to gene
 
 ## Using the device flow to generate a user access token
 
-> [!NOTE]
-> The device flow is in {% data variables.release-phases.public_preview %} and subject to change.
-
 If your app is headless or does not have access to a browser, you should use the device flow to generate a user access token. For example, CLI tools, simple Raspberry Pis, and desktop applications should use the device flow. For a tutorial that uses device flow, see [AUTOTITLE](/apps/creating-github-apps/guides/building-a-cli-with-a-github-app).
 
 Before you can use the device flow, you must first enable it in your app's settings. For more information on enabling device flow, see [AUTOTITLE](/apps/maintaining-github-apps/modifying-a-github-app).
 
-The device flow uses the OAuth 2.0 Device Authorization Grant.
+The device flow uses the [OAuth 2.0 Device Authorization Grant](https://datatracker.ietf.org/doc/html/rfc8628).
 
 1. Send a `POST` request to `{% data variables.product.oauth_host_code %}/login/device/code` along with a `client_id` query parameter. The client ID is different from the app ID. You can find the client ID on the settings page for your app. For more information about navigating to the settings page for your {% data variables.product.prodname_github_app %}, see [AUTOTITLE](/apps/maintaining-github-apps/modifying-a-github-app-registration#navigating-to-your-github-app-settings).
 1. {% data variables.product.company_short %} will give a response that includes the following query parameters:

content/copilot/concepts/agents/coding-agent/about-coding-agent.md

@@ -55,7 +55,7 @@ When used effectively, {% data variables.copilot.copilot_coding_agent %} offers
 
 ### {% data variables.copilot.copilot_coding_agent %} versus agent mode
 
-{% data variables.copilot.copilot_coding_agent %} is distinct from the "agent mode" feature available in your IDE. {% data variables.copilot.copilot_coding_agent %} works autonomously in a {% data variables.product.prodname_actions %}-powered environment to complete development tasks assigned through {% data variables.product.github %} issues or {% data variables.copilot.copilot_chat %} prompts, and creates pull requests with the results. In contrast, agent mode in your IDE makes autonomous edits directly in your local development environment. For more information about agent mode, see [AUTOTITLE](/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide?tool=visualstudio#copilot-edits-1).
+{% data variables.copilot.copilot_coding_agent %} is distinct from the "agent mode" feature available in your IDE. {% data variables.copilot.copilot_coding_agent %} works autonomously in a {% data variables.product.prodname_actions %}-powered environment to complete development tasks assigned through {% data variables.product.github %} issues or {% data variables.copilot.copilot_chat %} prompts, and creates pull requests with the results. In contrast, agent mode in your IDE makes autonomous edits directly in your local development environment. For more information about agent mode, see [AUTOTITLE](/copilot/using-github-copilot/copilot-chat/asking-github-copilot-questions-in-your-ide).
 
 ### Streamlining software development with {% data variables.copilot.copilot_coding_agent %}
 

content/copilot/how-tos/chat-with-copilot/chat-in-ide.md

@@ -119,23 +119,37 @@ In addition to submitting prompts through the chat view, you can submit prompts
 
 See [inline chat](https://code.visualstudio.com/docs/copilot/copilot-chat#_inline-chat), [quick chat](https://code.visualstudio.com/docs/copilot/copilot-chat#_quick-chat), and [chat smart actions](https://code.visualstudio.com/docs/copilot/copilot-chat#_chat-smart-actions) in the {% data variables.product.prodname_vscode %} documentation for more details.
 
-## {% data variables.copilot.copilot_edits_short %}
+## {% data variables.copilot.copilot_chat_short %} chat modes
 
-Use {% data variables.copilot.copilot_edits_short %} to make changes across multiple files directly from a single {% data variables.copilot.copilot_chat_short %} prompt. {% data variables.copilot.copilot_edits_short %} has the following modes:
+You can use {% data variables.copilot.copilot_chat_short %} in the following modes:
+
+* [Ask mode](#ask-mode): to get answers to coding questions and get {% data variables.product.prodname_copilot_short %} to provide code suggestions.
+* [Edit mode](#edit-mode): to get {% data variables.product.prodname_copilot_short %} to make controlled edits to multiple files.
+* [Agent mode](#agent-mode): to get {% data variables.product.prodname_copilot_short %} to autonomously accomplish a set task.
+* [Plan mode](#plan-mode): to get {% data variables.product.prodname_copilot_short %} to create detailed implementation plans to ensure all requirements are met.
+
+To switch between modes, use the agents dropdown at the bottom of the chat view.
+
+### Ask mode
 
-* [Edit mode](#edit-mode) lets {% data variables.product.prodname_copilot_short %} make controlled edits to multiple files.
-* [Agent mode](#agent-mode) lets {% data variables.product.prodname_copilot_short %} autonomously accomplish a set task.
+Ask mode is optimized for answering questions about your codebase, coding, and general technology concepts. Use ask mode when you want to understand how something works, explore ideas, or get help with coding tasks. For larger changes across multiple files or more complex coding tasks, consider using edit mode or agent mode.
+
+#### Using ask mode
+
+1. If the chat view is not already displayed, select **Open Chat** from the {% data variables.copilot.copilot_chat_short %} menu.
+1. At the bottom of the chat view, select **Ask** from the agents dropdown.
+1. Type a prompt in the prompt box and press <kbd>Enter</kbd>.
 
 ### Edit mode
 
 {% data reusables.copilot.copilot-edits.edit-mode-description %}
 
 #### Using edit mode
 
-1. To start an edit session, select **Open Chat** from the {% data variables.copilot.copilot_chat_short %} menu.
-1. At the bottom of the chat panel, select **Edit** from the mode dropdown.
+1. If the chat view is not already displayed, select **Open Chat** from the {% data variables.copilot.copilot_chat_short %} menu.
+1. At the bottom of the chat view, select **Edit** from the agents dropdown.
 
-   ![Screenshot of the {% data variables.copilot.copilot_chat_short %} mode dropdown. The "Edit" option is outlined in dark orange.](/assets/images/help/copilot/chat-mode-vscode.png)
+   ![Screenshot of the {% data variables.copilot.copilot_chat_short %} agents dropdown. The "Edit" option is outlined in dark orange.](/assets/images/help/copilot/chat-mode-vscode.png)
 
 1. Optionally, add relevant files to the _working set_ to indicate to {% data variables.product.prodname_copilot %} which files you want to work on.
 1. Submit a prompt. In response to your prompt, {% data variables.copilot.copilot_edits_short %} determines which files in your _working set_ to change and adds a short description of the change.
@@ -149,8 +163,8 @@ For more detailed instructions, see [{% data variables.copilot.copilot_edits_sho
 
 #### Using agent mode
 
-1. To start an edit session, select **Open Chat** from the {% data variables.copilot.copilot_chat_short %} menu.
-1. At the bottom of the chat panel, select **Agent** from the mode dropdown.
+1. If the chat view is not already displayed, select **Open Chat** from the {% data variables.copilot.copilot_chat_short %} menu.
+1. At the bottom of the chat view, select **Agent** from the agents dropdown.
 1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
 1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
 
@@ -160,6 +174,35 @@ For more information, see [{% data variables.copilot.copilot_edits_short %}](htt
 
 {% data reusables.copilot.copilot-edits.agent-mode-requests %}
 
+### Plan mode
+
+> [!NOTE]
+> Plan mode in {% data variables.product.prodname_vscode_shortname %} is currently in {% data variables.release-phases.public_preview %} and subject to change.
+
+Plan mode helps you to create detailed implementation plans before executing them. This ensures that all requirements are considered and addressed before any code changes are made. The plan agent does not make any code changes until the plan is reviewed and approved by you. Once approved, you can hand off the plan to the default agent or save it for further refinement, review, or team discussions.
+
+The plan agent is designed to:
+
+* Research the task comprehensively using read-only tools and codebase analysis to identify requirements and constraints.
+* Break down the task into manageable, actionable steps and include open questions about ambiguous requirements.
+* Present a concise plan draft, based on a standardized plan format, for user review and iteration.
+
+#### Using plan mode
+
+1. If the chat view is not already displayed, select **Open Chat** from the {% data variables.copilot.copilot_chat_short %} menu.
+1. At the bottom of the chat view, select **Plan** from the agents dropdown.
+1. Enter a task for which you want to create a plan, then press <kbd>Enter</kbd>.
+
+   The plan agent provides a high-level summary and a breakdown of steps, including any open questions for clarification.
+
+1. Review the plan and answer any questions the agent has asked.
+
+   You can iterate multiple times to clarify requirements, adjust scope, or answer questions.
+
+1. Once the plan is finalized, choose to save it or hand it off to an implementation agent to start coding, by using the corresponding controls.
+
+For more information, see [Planning in VS Code chat](https://code.visualstudio.com/docs/copilot/chat/chat-planning) in the {% data variables.product.prodname_vscode %} documentation.
+
 ## Using images in {% data variables.copilot.copilot_chat_short %}
 
 {% data reusables.copilot.using-images-in-chat %}
@@ -295,7 +338,7 @@ Use agent mode when you have a specific task in mind and want to enable {% data
 ### Using agent mode
 
 1. In the {% data variables.product.prodname_vs %} menu bar, click **View**, then click **{% data variables.copilot.copilot_chat %}**.
-1. At the bottom of the chat panel, select **Agent** from the mode dropdown.
+1. At the bottom of the chat panel, select **Agent** from the agents dropdown.
 1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
 1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
 
@@ -518,7 +561,7 @@ To see all available slash commands, type `/` in the chat prompt box. For more i
 ### Using agent mode
 
 1. To open the chat view, click **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %} {% data variables.product.prodname_copilot_short %}** in the menu bar, then click **Open Chat**.
-1. At the bottom of the chat panel, select **Agent** from the mode dropdown.
+1. At the bottom of the chat panel, select **Agent** from the agents dropdown.
 1. Optionally, add relevant files to the _working set_ view to indicate to {% data variables.product.prodname_copilot_short %} which files you want to work on.
 1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
 1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
@@ -596,7 +639,7 @@ To see all available slash commands, type `/` in the chat prompt box.
 ### Using agent mode
 
 1. To open the {% data variables.copilot.copilot_chat_short %} panel, click the {% data variables.product.prodname_copilot_short %} icon ({% octicon "copilot" aria-hidden="true" aria-label="copilot" %}) in the status bar at the bottom of Eclipse, then click **Open Chat**.
-1. At the bottom of the chat panel, select **Agent** from the mode dropdown.
+1. At the bottom of the chat panel, select **Agent** from the agents dropdown.
 1. Submit a prompt. In response to your prompt, {% data variables.product.prodname_copilot_short %} streams the edits in the editor, updates the working set, and if necessary, suggests terminal commands to run.
 1. Review the changes. If {% data variables.product.prodname_copilot_short %} suggested terminal commands, confirm whether or not {% data variables.product.prodname_copilot_short %} can run them. In response, {% data variables.product.prodname_copilot_short %} iterates and performs additional actions to complete the task in your original prompt.
 

data/reusables/copilot/zero-budget-changes.md

@@ -1,12 +1,12 @@
-<!-- expires 2026-01-10 -->
+<!-- expires 2026-01-17 -->
 <!-- Check with HC on whether or not references to this reusable can be deleted.
 See pr 57549 for details. -->
 
 Accounts created **before August 22, 2025** have a default $0 budget for {% data variables.product.prodname_copilot_short %} premium requests. Premium requests over the allowance are rejected unless you edit or delete this budget.
 
 > [!IMPORTANT]
-> **Beginning November 18, 2025:**
+> **Beginning December 2, 2025:**
 >
 > **Account-level $0 {% data variables.product.prodname_copilot_short %} premium request budgets** for {% data variables.product.prodname_enterprise %} and {% data variables.product.prodname_team %} will be removed. See [Upcoming removal of Copilot premium request $0 budgets for enterprise and team accounts](https://github.blog/changelog/2025-09-17-upcoming-removal-of-copilot-premium-request-0-budgets-for-enterprise-and-team-accounts/) in the {% data variables.product.github %} changelog.
 
-<!-- end expires 2026-01-10 -->
+<!-- end expires 2026-01-17 -->

src/graphql/data/fpt/changelog.json

@@ -1,4 +1,20 @@
 [
+  {
+    "schemaChanges": [
+      {
+        "title": "The GraphQL schema includes these changes:",
+        "changes": [
+          "<p>Type <code>RequiredReviewerConfiguration</code> was added</p>",
+          "<p>Type <code>RequiredReviewerConfigurationInput</code> was added</p>",
+          "<p>Field <code>requiredReviewers</code> was added to object type <code>PullRequestParameters</code></p>",
+          "<p>Input field <code>requiredReviewers</code> of type '[RequiredReviewerConfigurationInput!]<code>was added to input object type</code>PullRequestParametersInput'</p>"
+        ]
+      }
+    ],
+    "previewChanges": [],
+    "upcomingChanges": [],
+    "date": "2025-11-13"
+  },
   {
     "schemaChanges": [
       {

src/graphql/data/fpt/schema.docs.graphql

@@ -41909,6 +41909,13 @@ type PullRequestParameters {
   All conversations on code must be resolved before a pull request can be merged.
   """
   requiredReviewThreadResolution: Boolean!
+
+  """
+  This field is in beta and subject to change. A collection of reviewers and
+  associated file patterns. Each reviewer has a list of file patterns which
+  determine the files that reviewer is required to review.
+  """
+  requiredReviewers: [RequiredReviewerConfiguration!]
 }
 
 """
@@ -41950,6 +41957,13 @@ input PullRequestParametersInput {
   All conversations on code must be resolved before a pull request can be merged.
   """
   requiredReviewThreadResolution: Boolean!
+
+  """
+  This argument is in beta and subject to change. A collection of reviewers and
+  associated file patterns. Each reviewer has a list of file patterns which
+  determine the files that reviewer is required to review.
+  """
+  requiredReviewers: [RequiredReviewerConfigurationInput!]
 }
 
 """
@@ -54516,6 +54530,50 @@ input RequiredDeploymentsParametersInput {
   requiredDeploymentEnvironments: [String!]!
 }
 
+"""
+A reviewing team, and file patterns describing which files they must approve changes to.
+"""
+type RequiredReviewerConfiguration {
+  """
+  Array of file patterns. Pull requests which change matching files must be
+  approved by the specified team. File patterns use fnmatch syntax.
+  """
+  filePatterns: [String!]!
+
+  """
+  Minimum number of approvals required from the specified team. If set to zero,
+  the team will be added to the pull request but approval is optional.
+  """
+  minimumApprovals: Int!
+
+  """
+  Node ID of the team which must review changes to matching files.
+  """
+  reviewerId: ID!
+}
+
+"""
+A reviewing team, and file patterns describing which files they must approve changes to.
+"""
+input RequiredReviewerConfigurationInput {
+  """
+  Array of file patterns. Pull requests which change matching files must be
+  approved by the specified team. File patterns use fnmatch syntax.
+  """
+  filePatterns: [String!]!
+
+  """
+  Minimum number of approvals required from the specified team. If set to zero,
+  the team will be added to the pull request but approval is optional.
+  """
+  minimumApprovals: Int!
+
+  """
+  Node ID of the team which must review changes to matching files.
+  """
+  reviewerId: ID!
+}
+
 """
 Represents a required status check for a protected branch, but not any specific run of that check.
 """