Merge pull request #40532 from github/repo-sync

Repo sync

Author: docs-bot

CHANGELOG.md

@@ -66,7 +66,7 @@ See: [Configure custom instructions for GitHub Copilot](https://docs.github.com/
 
 In addition to repository-wide custom instructions, specified in the `.github/copilot-instructions.md` file, Copilot Code Review now supports:
 
-* Path-specific custom instructions, specified in `.github/instructions/NAME.instructions.md` files.
+* Path-specific custom instructions, specified in `.github/instructions/**/NAME.instructions.md` files.
 * Custom instructions specified in the organization settings for Copilot.
 
 We have updated several articles in the GitHub documentation accordingly. We have also made changes to clarify the difference between the various types of custom instructions for Copilot Code Review, Copilot Chat, and Copilot Coding Agent.

content/copilot/how-tos/use-copilot-agents/coding-agent/extend-coding-agent-with-mcp.md

@@ -222,6 +222,54 @@ The [Cloudflare MCP server](https://github.com/cloudflare/mcp-server-cloudflare)
 }
 ```
 
+### Example: Azure DevOps
+
+The [Azure DevOps MCP server](https://github.com/microsoft/azure-devops-mcp) creates a seamless connection between {% data variables.product.prodname_copilot_short %} and your Azure DevOps services, including work items, pipelines or documentation.
+
+To use the Azure DevOps MCP server with {% data variables.copilot.copilot_coding_agent %}, you must update the repository's copilot-setup-steps.yml file to include an Azure login workflow step.
+
+1. Configure OIDC in a Microsoft Entra application, trusting {% data variables.product.github %}. See [Use the Azure Login action with OpenID Connect](https://learn.microsoft.com/en-us/azure/developer/github/connect-from-azure-openid-connect).
+1. Setup access to Azure DevOps organization and projects for the application identity. See [Add organization users and manage access](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/add-organization-users).
+1. Add a `.github/workflows/copilot-setup-steps.yml` Actions workflow file in your repository if you do not already have one.
+1. Add an Azure login step to the `copilot-setup-steps` workflow job.
+   ```yaml copy
+   on:
+     workflow_dispatch:
+   permissions:
+     id-token: write
+     contents: read
+   jobs:
+     copilot-setup-steps:
+       runs-on: ubuntu-latest
+       permissions:
+         id-token: write
+         contents: read
+       environment: copilot
+       steps:
+         - name: Azure login
+           uses: azure/login@a457da9ea143d694b1b9c7c869ebb04ebe844ef5
+           with:
+             client-id: {% raw %}${{ secrets.AZURE_CLIENT_ID }}{% endraw %}
+             tenant-id: {% raw %}${{ secrets.AZURE_TENANT_ID }}{% endraw %}
+             allow-no-subscriptions: true
+   ```
+   This configuration ensures the `azure/login` action is executed when {% data variables.copilot.copilot_coding_agent %} runs.
+1. In your repository’s {% data variables.product.prodname_copilot_short %} environment, add secrets for your `AZURE_CLIENT_ID` and `AZURE_TENANT_ID`.
+1. Configure the Azure DevOps MCP server by adding an `ado` object to your MCP configuration with defined tools you want {% data variables.copilot.copilot_coding_agent %} to use.
+  ```json copy
+  {
+    "mcpServers": {
+      "ado": {
+        "type": "local",
+        "command": "npx",
+        "args": ["-y", "@azure-devops/mcp", "<your-azure-devops-organization>", "-a", "azcli"],
+        "tools": ["wit_get_work_item", "wit_get_work_items_batch_by_ids", ...]
+      }
+    }
+  }
+   ```
+
+
 ## Reusing your MCP configuration from {% data variables.product.prodname_vscode %}
 
 If you have already configured MCP servers in {% data variables.product.prodname_vscode_shortname %}, you can leverage a similar configuration for {% data variables.copilot.copilot_coding_agent %}.

content/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md

@@ -61,8 +61,8 @@ Different size limits per repository apply to the compressed archive, depending
 
 Limit | GHES <3.8.0 | GHES 3.8.x-3.11.x | GHES 3.12.x | GHES 3.13.0+
 ----- | ----------- | ----------------- | ----------- | ------------
-Git source | 2GB | 10GB | 20GB | 40GB (public preview)
-Metadata | 2GB | 10GB | 20GB | 40GB (public preview)
+Git source | 2GiB | 10GiB | 20GiB | 40GiB (public preview)
+Metadata | 2GiB | 10GiB | 20GiB | 40GiB (public preview)
 
 ### Data that is not migrated
 
@@ -122,7 +122,7 @@ When you migrate a repository, either directly or as part of an organization mig
     * Allow merge commits (commit message setting is reset to the default message)
     * Allow squash merging (commit message setting is reset to the default message)
     * Allow rebase merging
-* Releases (up to 10 GB per repository)
+* Releases (up to 10 GiB per repository)
 * User history for the above data
 * Attachments (see [AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/attaching-files))
 
@@ -147,7 +147,7 @@ When you migrate a repository directly, teams and team access to repositories ar
 ### Limitations of {% data variables.product.prodname_importer_proper_name %}
 
 * {% data reusables.enterprise-migration-tool.git-repo-size-limit %}
-* **40 GB limit for metadata ({% data variables.release-phases.public_preview %}):** The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 40 GB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration.
+* **40 GiB limit for metadata ({% data variables.release-phases.public_preview %}):** The {% data variables.product.prodname_importer_secondary_name %} cannot migrate repositories with more than 40 GiB of metadata. Metadata includes issues, pull requests, releases, and attachments. In most cases, large metadata is caused by binary assets attached to releases. You can exclude releases from the migration with the `migrate-repo` command's `--skip-releases` flag, and then move your releases manually after the migration.
 {% data reusables.enterprise-migration-tool.limitations-of-migration-tooling %}
 
 ## Getting started

data/reusables/enterprise-migration-tool/git-repo-size-limit.md

@@ -1 +1 @@
-**40 GB size limit for a Git repository ({% data variables.release-phases.public_preview %}):** This limit applies only to the source code. To check if the repository archive is over the limit, use the [git-sizer](https://github.com/github/git-sizer) tool and review the total blob size in the output. The git-sizer tool also helps to identify potential issues related to large files, blob size, commit size, and tree counts that could impact migrations.
+**40 GiB size limit for a Git repository ({% data variables.release-phases.public_preview %}):** This limit applies only to the source code. To check if the repository archive is over the limit, use the [git-sizer](https://github.com/github/git-sizer) tool and review the total blob size in the output. The git-sizer tool also helps to identify potential issues related to large files, blob size, commit size, and tree counts that could impact migrations.

data/reusables/enterprise-migration-tool/limitations-of-migration-tooling.md

@@ -1,4 +1,4 @@
-* **400 MB file size limit:** When migrating a repository with {% data variables.product.prodname_importer_proper_name %}, no single file in your Git repository can be larger than 400 MB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files).
+* **400 MiB file size limit:** When migrating a repository with {% data variables.product.prodname_importer_proper_name %}, no single file in your Git repository can be larger than 400 MiB. Consider using {% data variables.large_files.product_name_short %} for storing large files. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-large-files).
 * **{% data variables.large_files.product_name_short %} objects not migrated:** The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete. For more information, see [AUTOTITLE](/repositories/creating-and-managing-repositories/duplicating-a-repository#mirroring-a-repository-that-contains-git-large-file-storage-objects).
 * **Follow-up tasks required:** When migrating between {% data variables.product.prodname_dotcom %} products, certain settings are not migrated and must be reconfigured in the new repository. For a list of follow-up tasks you'll need to complete after each migration, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products#completing-follow-up-tasks).
 * **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.

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

@@ -1616,7 +1616,7 @@
       },
       {
         "category": "teams",
-        "slug": "list-external-groups-in-an-organization",
+        "slug": "list-external-groups-available-to-an-organization",
         "subcategory": "external-groups",
         "verb": "get",
         "requestPath": "/orgs/{org}/external-groups",

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

@@ -5191,7 +5191,7 @@
       "requestPath": "/orgs/{org}/external-group/{group_id}"
     },
     {
-      "slug": "list-external-groups-in-an-organization",
+      "slug": "list-external-groups-available-to-an-organization",
       "subcategory": "external-groups",
       "verb": "get",
       "requestPath": "/orgs/{org}/external-groups"

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

@@ -2124,7 +2124,7 @@
       },
       {
         "category": "teams",
-        "slug": "list-external-groups-in-an-organization",
+        "slug": "list-external-groups-available-to-an-organization",
         "subcategory": "external-groups",
         "verb": "get",
         "requestPath": "/orgs/{org}/external-groups",

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

@@ -5395,7 +5395,7 @@
       "requestPath": "/orgs/{org}/external-group/{group_id}"
     },
     {
-      "slug": "list-external-groups-in-an-organization",
+      "slug": "list-external-groups-available-to-an-organization",
       "subcategory": "external-groups",
       "verb": "get",
       "requestPath": "/orgs/{org}/external-groups"

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

@@ -5893,7 +5893,7 @@
       "requestPath": "/orgs/{org}/external-group/{group_id}"
     },
     {
-      "slug": "list-external-groups-in-an-organization",
+      "slug": "list-external-groups-available-to-an-organization",
       "subcategory": "external-groups",
       "verb": "get",
       "requestPath": "/orgs/{org}/external-groups"