Merge pull request #44888 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/concepts/identity-and-access-management/setup-user.md

@@ -43,6 +43,18 @@ Enterprise recovery codes are not the same as personal two-factor authentication
 
 {% data reusables.enterprise-accounts.emu-password-reset-session %}
 
+## Can I change the email address for the setup user?
+
+You can change the email address at any time while signed in to the setup user account. This is useful if the original recipient has left your organization or if you need to route notifications to a different address.
+
+> [!WARNING]
+> Ensure you have access to the new email address before making this change. You'll need to verify the new address via email.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+1. Under "Update email address *", type a new email address and click **Update**.
+1. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
+
 ## Can I delete the setup user?
 
 The setup user **cannot** be deleted, because it is essential for maintaining authentication and provisioning. The only way to remove the setup user is to delete your enterprise account. See [AUTOTITLE](/admin/managing-your-enterprise-account/deleting-an-enterprise-account).

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

@@ -62,10 +62,14 @@ The models available for {% data variables.product.prodname_copilot_short %} var
 * {% data variables.copilot.copilot_gpt_54_nano %}
 * {% data variables.copilot.copilot_gpt_55 %}
 * {% data variables.copilot.copilot_claude_haiku_45 %}
-* {% data variables.copilot.copilot_claude_sonnet_45 %}
 * {% data variables.copilot.copilot_claude_opus_45 %}
-* {% data variables.copilot.copilot_claude_sonnet_46 %}
 * {% data variables.copilot.copilot_claude_opus_46 %}
+* {% data variables.copilot.copilot_claude_opus_47 %}
+* {% data variables.copilot.copilot_claude_opus_48 %}
+* {% data variables.copilot.copilot_claude_sonnet_45 %}
+* {% data variables.copilot.copilot_claude_sonnet_46 %}
+* {% data variables.copilot.copilot_gemini_31_pro %}
+* {% data variables.copilot.copilot_gemini_35_flash %}
 
 ## Pricing changes
 

content/billing/concepts/product-billing/github-actions.md

@@ -47,7 +47,9 @@ Each {% data variables.copilot.copilot_code-review_short %} consumes {% data var
 * **Continuous billing:** Storage charges accrue every hour based on your actual usage throughout the month
 * **Monthly total:** Your bill reflects the total storage used throughout the month, measured in GB-Hours
 * **Included amount:** The free storage allowance for your plan (for example, 50 GB on the Enterprise plan) is converted to an hourly rate for billing calculations
-* **Shared storage:** Actions artifacts, Actions caches, and {% data variables.product.prodname_registry %} storage all share the same pooled allowance. For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-packages).
+* **Shared storage:** Actions artifacts and {% data variables.product.prodname_registry %} storage share the same pooled allowance. See [AUTOTITLE](/billing/concepts/product-billing/github-packages).
+* **Cache storage:** Actions cache storage is a separate allowance of 10 GB per repository. Cache storage is not shared with artifacts or {% data variables.product.prodname_registry %}.
+* **Custom image storage:** Storage for custom images used with {% data variables.actions.github_hosted_larger_runners %} has its own included allowance based on your plan.
 
 ### Understanding current vs. accrued storage
 
@@ -112,8 +114,7 @@ For example:
 * If you run a workflow on a Linux runner and it takes 10 minutes to complete, you'll use 10 minutes of the repository owner's allowance. If the workflow generates a 10 MB artifact, then you'll also use 10 MB of the repository owner's artifact storage allowance.
 * If you run a workflow that normally takes 10 minutes and it fails after 5 minutes because a dependency isn't available, you'll use 5 minutes of the repository owner's allowance. If you fix the problem and re-run the workflow successfully, in total you'll use 15 minutes of the repository owner's allowance.
 * If you run a workflow that generates many log files and a long job summary, these files do not count towards the repository owner's artifact storage allowance.
-* Cache storage usage is measured by the peak usage for each hour. Included usage is 10 GB per repository. For a given hour, if a repository has a peak cache usage of 15 GB, then the repository owner will be charged for the 5 GB of usage above the 10 GB included for that hour. The repository owner will only be charged if the repository cache storage limit has been configured higher than the included usage.
-* Additional cache storage is $0.07 per GiB, per month.
+* Cache storage usage is measured by the peak usage for each hour. The included allowance is 10 GB per repository. For a given hour, if a repository has a peak cache usage of 15 GB, then the repository owner will be charged for the 5 GB of usage above the 10 GB included for that repository. The repository owner will only be charged if the repository cache storage limit has been configured higher than the included usage.
 
 ## Free use of {% data variables.product.prodname_actions %}
 
@@ -130,7 +131,7 @@ The use of standard {% data variables.product.github %}-hosted runners is free:
 > [!NOTE]
 >
 > * Larger runners are always charged for, even when used by public repositories or when you have quota available from your plan.
-> * The storage amounts shown are **shared** with {% data variables.product.prodname_registry %}. This means your total storage across Actions artifacts, Actions caches, and Packages cannot exceed the included amount for your plan.
+> * The artifact storage amounts shown are **shared** with {% data variables.product.prodname_registry %}. This means your total storage across Actions artifacts and {% data variables.product.prodname_registry %} storage cannot exceed the included amount for your plan. Cache storage and custom image storage are separate allowances.
 > * {% data variables.copilot.copilot_code-review_short %} consumes {% data variables.product.prodname_actions %} minutes on private repositories. For public repositories, {% data variables.product.prodname_actions %} minutes remain free.
 
 ## Using more than your included quota
@@ -159,6 +160,16 @@ For example, jobs that run on Windows and macOS runners hosted by {% data variab
 
 For full details of minute costs for different types of runners, see [AUTOTITLE](/billing/reference/actions-runner-pricing).
 
+### Storage pricing
+
+Usage beyond your included allowances is billed at the following rates:
+
+| Storage type | Price per GB/month |
+| --- | --- |
+| Shared storage (artifacts and {% data variables.product.prodname_registry %}) | $0.25 USD |
+| Actions cache | $0.07 USD |
+| Custom image storage | $0.07 USD |
+
 ### Example minutes cost calculation for {% data variables.product.github %}-hosted runners
 
 For example, if your organization uses {% data variables.product.prodname_team %}, using 5,000 minutes beyond the included quota on {% data variables.product.github %}-hosted runners would have a total actions minutes cost of $38 USD currently, if you used baseline Linux and Windows runners.

content/billing/concepts/product-billing/github-packages.md

@@ -58,7 +58,7 @@ Plan | Storage | Data transfer (per month)
 
 {% endrowheaders %}
 
-The storage amounts shown are **shared** with {% data variables.product.prodname_actions %}. This means your total storage across Packages, Actions artifacts, and Actions caches cannot exceed the included amount for your plan.
+The storage amounts shown are **shared** with {% data variables.product.prodname_actions %} artifacts. This means your total storage across Packages and Actions artifacts cannot exceed the included amount for your plan.
 
 > [!NOTE]
 > * **Billing for container image storage:** Container image storage and bandwidth for the {% data variables.product.prodname_container_registry %} is currently free. If you use {% data variables.product.prodname_container_registry %}, you'll be informed at least one month in advance of any change to this policy. For more information about the {% data variables.product.prodname_container_registry %}, see [AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-container-registry).

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

@@ -12,7 +12,7 @@ contentType: concepts
 ---
 
 > [!NOTE]
-> Agent skills work with {% data variables.copilot.copilot_cloud_agent %}, {% data variables.copilot.copilot_code-review_short %}, the {% data variables.copilot.copilot_cli %}, the {% data variables.copilot.github_copilot_app %}, and agent mode in {% data variables.product.prodname_vscode %}.
+> Agent skills work with {% data variables.copilot.copilot_cloud_agent %}, {% data variables.copilot.copilot_code-review_short %}, the {% data variables.copilot.copilot_cli %}, the {% data variables.copilot.github_copilot_app %}, and agent mode in {% data variables.product.prodname_vscode %} and {% data variables.jetbrains.prodname_jetbrains_ides %}.
 
 ## About agent skills
 

content/copilot/concepts/agents/copilot-cli/chronicle.md

@@ -25,6 +25,8 @@ This session data powers several features, available from {% data variables.copi
 
 With user-scoped queries, you can only query your own sessions—no one else can access your session data.
 
+In {% data variables.jetbrains.prodname_jetbrains_ides %}, `/chronicle` is available in interactive {% data variables.copilot.copilot_cli_short %} sessions, so you can review session history and generate insights without leaving the IDE.
+
 This conceptual article explains how session data is stored and synced, and how you can use it to enhance your workflow. For a practical guide to resuming a session, asking {% data variables.product.prodname_copilot_short %} about your CLI sessions, and using the `/chronicle` slash command, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/chronicle). For querying sessions from {% data variables.product.prodname_vscode_shortname %}, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/use-copilot-agents/manage-and-track-agents).
 
 ## How session data is stored
@@ -77,6 +79,8 @@ For the full list of `/session` subcommands, see [AUTOTITLE](/copilot/reference/
 
 The `/chronicle` slash command provides purpose-built subcommands for generating insights from your session history, including standup reports, personalized tips, cost analysis, and suggestions for improving your custom instructions. For the full list of subcommands and usage examples, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/chronicle#using-the-chronicle-slash-command).
 
+If you use {% data variables.copilot.copilot_cli_short %} in {% data variables.jetbrains.prodname_jetbrains_ides %}, these `/chronicle` subcommands are available from the interactive CLI session you open in the IDE.
+
 ## When to use session data
 
 * **At the start of your day**: Run `/chronicle standup last 3 days` to generate a summary of recent work instead of reconstructing it manually.

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

@@ -372,6 +372,18 @@ To share feedback about {% data variables.copilot.copilot_chat_short %}, you can
 
 {% data reusables.copilot.chat-access-denied %}
 
+## {% data variables.copilot.copilot_chat_short %} agents
+
+The agent picker in the {% data variables.copilot.copilot_chat_short %} panel lets you choose which agent drives your conversation. To switch agents, use the Agents dropdown at the bottom of the chat panel.
+
+The following agents are available:
+
+* **Agent mode** (default): Full agentic experience with autonomous task execution.
+* **Ask mode**: Get quick answers and assistance without making code changes.
+* **Plan mode**: Collaborate on planning before implementation—{% data variables.product.prodname_copilot_short %} analyzes your request and builds a structured plan for your review.
+* **{% data variables.copilot.copilot_cli_short %}**: Runs {% data variables.product.prodname_copilot_short %} through {% data variables.copilot.copilot_cli_short %}, providing a terminal-first agentic experience with support for multiple isolation modes, live session progress, and tool call visibility. For more information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-copilot-cli).
+* **Custom agents**: Use personalized agents tailored to your specific needs. For more information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-custom-agents).
+
 ## Submitting prompts
 
 You can ask {% data variables.copilot.copilot_chat_short %} to give you code suggestions, explain code, generate unit tests, and suggest code fixes.

content/copilot/how-tos/copilot-cli/use-copilot-cli/steer-remotely.md

@@ -32,11 +32,12 @@ This article explains how to enable and use remote control. For more conceptual
 
 ## Enabling remote control for a session
 
-You can enable remote control in three ways:
+You can enable remote control in several ways:
 
 * With a slash command during an interactive session.
 * With a command-line option when you start {% data variables.copilot.copilot_cli_short %}.
 * By configuring the CLI to enable remote control by default for all interactive sessions.
+* From JetBrains IDE settings before you start a session.
 
 ### Using the `/remote` slash command
 
@@ -79,6 +80,17 @@ copilot --no-remote
 > [!NOTE]
 > The command-line options `--remote` and `--no-remote` always take precedence over the `remote` setting in the settings file.
 
+### Using JetBrains IDE settings
+
+If you use {% data variables.copilot.copilot_cli_short %} from a JetBrains IDE, you can enable remote control from the IDE before you start a session.
+
+{% data reusables.copilot.jetbrains-settings %}
+{% data reusables.copilot.jetbrains-tools %}, then click **Chat**.
+1. Select **Enable Copilot CLI Remote**.
+1. Start an interactive {% data variables.copilot.copilot_cli_short %} session from the IDE.
+
+When this setting is enabled, you can use `/remote` in the session at any time to view the current remote control status or redisplay the links and QR code for accessing the session remotely.
+
 ## Accessing a session from {% data variables.product.prodname_dotcom_the_website %}
 
 When you enable remote control, the CLI displays a link to the session on {% data variables.product.prodname_dotcom_the_website %}.
@@ -157,4 +169,3 @@ Remote control is disabled by default, but may be enabled in your {% data variab
 ## Further reading
 
 * [{% data variables.copilot.copilot_cli_short %} sessions in {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/docs/copilot/agents/copilot-cli) in the {% data variables.product.prodname_vscode_shortname %} documentation.
-* [Enable {% data variables.copilot.copilot_cli_short %} remote control](https://github.com/microsoft/copilot-intellij-feedback/wiki/Enable-Copilot-CLI-Remote-Control) for JetBrains IDEs, in the `microsoft/copilot-intellij-feedback` repository.

content/copilot/how-tos/set-up/install-copilot-extension.md

@@ -70,7 +70,7 @@ The following procedure will guide you through installation of the {% data varia
 
    {% data reusables.copilot.jetbrains-compatible-ides %}
 
-1. Install the {% data variables.product.prodname_copilot %} plugin for JetBrains. See [{% data variables.product.prodname_copilot %} plugin](https://plugins.jetbrains.com/plugin/17718-github-copilot?ref_product=copilot&ref_type=engagement&ref_style=text) in the JetBrains Marketplace.
+1. In your JetBrains IDE, open the **Plugins** settings, search the **Marketplace** for the {% data variables.product.prodname_copilot %} plugin, then click **Install**. For more information, see [{% data variables.product.prodname_copilot %} plugin](https://plugins.jetbrains.com/plugin/17718-github-copilot?ref_product=copilot&ref_type=engagement&ref_style=text) in the JetBrains Marketplace.
 
 1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**.
 
@@ -84,7 +84,9 @@ The following procedure will guide you through installation of the {% data varia
 
    ![Screenshot of the "Sign in to {% data variables.product.prodname_dotcom %}" dialog. A device code is displayed above a button labeled "Copy and Open".](/assets/images/help/copilot/device-code-copy-and-open.png)
 
-1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
+1. A device activation window will open in your browser. If prompted to sign in to {% data variables.product.prodname_dotcom %}, sign in with your {% data variables.product.github %} account, or click **Continue with Google** or **Continue with Apple**.
+
+1. Paste the device code, then click **Continue**.
 
 1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
 

content/copilot/how-tos/troubleshoot-copilot/view-logs.md

@@ -65,6 +65,23 @@ If you find the log file doesn't contain enough information to resolve an issue,
 1. Keep using your IDE until you encounter the issue again, then collect the log file as described in [Collecting log files](#collecting-log-files).
 1. When you have the information you need, disable debug mode by removing `#com.github.copilot:trace` from the "Custom Debug Log Configuration" window.
 
+## Using the Agent Debug Panel
+
+> [!NOTE]
+> This feature is in {% data variables.release-phases.public_preview %} and subject to change.
+
+The Agent Debug Panel shows a chronological event log of agent interactions during a {% data variables.copilot.copilot_cli_short %} session. Use the panel to debug {% data variables.copilot.custom_agents_short %} and subagent workflows.
+
+1. Open {% data variables.copilot.copilot_chat_short %} in your JetBrains IDE.
+1. In the agent picker, select {% data variables.copilot.copilot_cli_short %}.
+1. In the top-right corner of the chat panel, click the settings icon, then click **Agent Debug Panel**.
+1. For full support across current and historical sessions, enable debug file logging.
+   1. Open **Settings**.
+   1. In the sidebar, click **Tools**, then **{% data variables.product.prodname_copilot_short %}**, then **Chat**.
+   1. Select **Enable Agent debug File Logging**.
+
+If you use {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %}, ask your administrator to enable the Editor preview features policy before you use this feature.
+
 ## Viewing network connectivity diagnostics logs
 
 If you encounter problems connecting to {% data variables.product.prodname_copilot %} due to network restrictions, firewalls, or your proxy setup, use the following troubleshooting steps.