Merge branch 'main' into codespace-friendly-system-6wxww7554q63xrgx

Author: nongkibki

.devcontainer/Dockerfile

@@ -1,5 +1,5 @@
 # To find available Node images, see https://mcr.microsoft.com/en-us/product/devcontainers/javascript-node/tags
 
 # [Choice] Node.js version
-ARG VARIANT="dev-22-bullseye"
+ARG VARIANT="dev-24-bullseye"
 FROM mcr.microsoft.com/devcontainers/javascript-node:${VARIANT}

.devcontainer/devcontainer.json

@@ -6,7 +6,7 @@
   "build": {
     "dockerfile": "Dockerfile",
     // Update 'VARIANT' to pick a Node version
-    "args": { "VARIANT": "22" }
+    "args": { "VARIANT": "24" }
   },
 
   // Install features. Type 'feature' in the VS Code command palette for a full list.

CHANGELOG.md

@@ -1,5 +1,13 @@
 # Docs changelog
 
+**11 September 2025**
+
+You can now enable automatic Copilot code review with its own standalone repository rule. We've updated the documentation accordingly.
+
+See [Configuring automatic code review by GitHub Copilot](https://docs.github.com/copilot/how-tos/use-copilot-agents/request-a-code-review/configure-automatic-review).
+
+<hr>
+
 **4 September 2025**
 
 We've updated the documentation to remove references to Copilot coding guidelines.

Dockerfile

@@ -17,7 +17,7 @@ FROM ghcr.io/github/gh-base-image/gh-base-noble:20250805-204228-g50c20871f AS ba
 # Ubuntu's apt-get install nodejs is _very_ outdated
 # Must run as root
 RUN apt-get -qq update && apt-get -qq install --no-install-recommends curl git \
-  && curl -sL https://deb.nodesource.com/setup_22.x | bash - \
+  && curl -sL https://deb.nodesource.com/setup_24.x | bash - \
   && apt-get install -y nodejs \
   && node --version
 

assets/images/help/copilot/vsc-manage-models-list.png

@@ -405,7 +405,7 @@ on:
 > * {% data reusables.actions.branch-requirement %}
 > * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
 
-Runs your workflow when a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to cards or columns in a {% data variables.projects.projects_v1_board %}, use the [`project_card`](#project_card) or [`project_column`](#project_column) events instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the {% data variables.projects.projects_v1_board %} APIs, see [AUTOTITLE](/graphql/reference/objects#project) in the GraphQL API documentation or [AUTOTITLE](/rest/projects).
+Runs your workflow when a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to cards or columns in a {% data variables.projects.projects_v1_board %}, use the [`project_card`](#project_card) or [`project_column`](#project_column) events instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the {% data variables.projects.projects_v1_board %} APIs, see [AUTOTITLE](/graphql/reference/objects#project) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic).
 
 For example, you can run a workflow when a project has been `created` or `deleted`.
 
@@ -426,7 +426,7 @@ on:
 > * {% data reusables.actions.branch-requirement %}
 > * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
 
-Runs your workflow when a card on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or columns in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_column`](#project_column) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project card APIs, see [AUTOTITLE](/graphql/reference/objects#projectcard) in the GraphQL API documentation or [AUTOTITLE](/rest/projects/cards).
+Runs your workflow when a card on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or columns in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_column`](#project_column) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project card APIs, see [AUTOTITLE](/graphql/reference/objects#projectcard) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic/cards).
 
 For example, you can run a workflow when a project card has been `created` or `deleted`.
 
@@ -447,7 +447,7 @@ on:
 > * {% data reusables.actions.branch-requirement %}
 > * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
 
-Runs your workflow when a column on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or cards in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_card`](#project_card) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project column APIs, see [AUTOTITLE](/graphql/reference/objects#projectcolumn) in the GraphQL API documentation or [AUTOTITLE](/rest/projects#columns).
+Runs your workflow when a column on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or cards in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_card`](#project_card) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project column APIs, see [AUTOTITLE](/graphql/reference/objects#projectcolumn) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic#columns).
 
 For example, you can run a workflow when a project column has been `created` or `deleted`.
 
@@ -1002,7 +1002,7 @@ Notifications for scheduled workflows are sent to the user who last modified the
 > [!NOTE]
 > For an enterprise with {% data variables.product.prodname_emus %}, triggering a scheduled workflow requires that the status of the `actor` user account associated with the workflow is currently active (i.e. not suspended or deleted).
 > * Scheduled workflows will not run if the last `actor` associated with the scheduled workflow has been deprovisioned by the {% data variables.product.prodname_emu %} identity provider (IdP). However, if the last `actor` {% data variables.product.prodname_emu %} has not been deprovisioned by the IdP, and has only been removed as a member from a given organization in the enterprise, scheduled workflows will still run with that user set as the `actor`.
-> * Similarly, for an enterprise without {% data variables.product.prodname_emus %}, removing a user from an organization will not prevent scheduled workflows which had that user as their `actor` from running.  
+> * Similarly, for an enterprise without {% data variables.product.prodname_emus %}, removing a user from an organization will not prevent scheduled workflows which had that user as their `actor` from running.
 > * Thus, the _user account's_ status, in both {% data variables.product.prodname_emu %} and non-{% data variables.product.prodname_emu %} scenarios, is what's important, _not_ the user's _membership status_ in the organization where the scheduled workflow is located.
 
 ## `status`

assets/images/help/copilot/vsc-manage-models-option.png

@@ -26,7 +26,7 @@ Your billing experience depends on whether your products are metered, volume-bas
 
 ## Billing cycles for metered products
 
-Metered products have a fixed **billing period** that runs from the first day of each month to the last day of the month.
+Metered products have a fixed **billing period** that starts at 00:00:00 UTC on the first day of each month and ends at 23:59:59 UTC on the last day of the month.
 
 At the end of each month, your metered usage is calculated and scheduled to be billed on your **bill cycle day**.
 

content/actions/reference/workflows-and-actions/events-that-trigger-workflows.md

@@ -69,4 +69,4 @@ The usage report contains the following fields.
 
 ## Receiving the report
 
-Usage reports are sent via email to the default email address associated with your {% data variables.product.github %} account.
+Usage reports are sent via email to the default email address associated with your {% data variables.product.github %} account. You can only request one usage report per account at a time.

content/billing/concepts/billing-cycles.md

@@ -61,7 +61,47 @@ These instructions are for {% data variables.product.prodname_vscode %}. For ins
 {% data reusables.copilot.chat-model-limitations-ide %}
 
 {% data reusables.copilot.open-chat-vs-code %}
-1. In the bottom right of the chat view, select the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} dropdown menu, then click the AI model of your choice.
+1. At the bottom of the chat view, select the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} dropdown menu, then click the AI model of your choice.
+
+## Adding more models
+
+You can expand the model options that are available to power {% data variables.copilot.copilot_chat_short %}. You can add models from:
+
+* **A model provider**—such as Anthropic, Gemini, OpenAI, and others.
+* **The AI Toolkit for {% data variables.product.prodname_vscode %}**.
+
+> [!NOTE] Using the AI Toolkit for {% data variables.product.prodname_vscode_shortname %} is in {% data variables.release-phases.public_preview %} and subject to change.
+
+### Prerequisites
+
+* Depending on the provider or model you choose, you may need to supply an API key, or model ID, from the provider, or a {% data variables.product.github %} {% data variables.product.pat_generic %} (PAT).
+* To add models from the AI Toolkit for {% data variables.product.prodname_vscode %}, you must <a href="vscode:extension/ms-windows-ai-studio.windows-ai-studio">install the AI Toolkit extension</a>.
+
+### Adding models
+
+1. In the {% data variables.product.prodname_copilot_short %} chat view, click the **CURRENT-MODEL** {% octicon "chevron-down" aria-hidden="true" aria-label="chevron-down" %} dropdown menu.
+1. Click **Manage Models**.
+
+   ![Screenshot of the 'Manage Models' option, highlighted with a dark orange outline.](/assets/images/help/copilot/vsc-manage-models-option.png)
+
+   A list of providers is displayed.
+
+   If you have installed the AI Toolkit, then additional providers, added via the AI Toolkit, are also listed.
+
+   ![Screenshot of the 'Manage Language Models' list.](/assets/images/help/copilot/vsc-manage-models-list.png)
+
+1. Click the provider whose model(s) you want to add.
+1. Depending on which provider you selected, you may be prompted to enter a {% data variables.product.github %} PAT, an API key for the provider, or a model ID for a specific model.
+
+   Enter the required information, then press <kbd>Enter</kbd>.
+
+   A list of available models is displayed.
+
+1. Select the model(s) you want to add, then click **OK**.
+
+The models you selected are now available in the model picker in the chat view.
+
+If you added a model from a provider via the AI Toolkit then the first time you use the model, you will be prompted to download it. You may also be prompted to authenticate with the provider.
 
 > [!TIP] If you're already using chat with {% data variables.copilot.copilot_auto_model_selection_short %}, you'll need to start a new chat session to switch models. To start a new session, in the top right of the chat view, click {% octicon "plus" aria-label="new chat" %} new chat.
 
@@ -137,3 +177,9 @@ To use multi-model {% data variables.copilot.copilot_chat_short %}, you must ins
 
 * [AUTOTITLE](/copilot/using-github-copilot/ai-models/changing-the-ai-model-for-copilot-code-completion)
 * [AUTOTITLE](/copilot/reference/ai-models/model-comparison)
+
+{% vscode %}
+
+* [AI language models in VS Code](https://code.visualstudio.com/docs/copilot/language-models#_bring-your-own-language-model-key) in the {% data variables.product.prodname_vscode %} documentation.
+
+{% endvscode %}