Merge branch 'main' into patch-10

Author: clarencepenz

.devcontainer/devcontainer.json

@@ -59,11 +59,13 @@
   },
 
   // Lifecycle commands
-  "onCreateCommand": "npm ci",
+  // Install dependencies then install Copilot CLI
+  "onCreateCommand": "npm ci && npm config set \"//npm.pkg.github.com/:_authToken=$GITHUB_TOKEN\" && npm config set \"@github:registry=https://npm.pkg.github.com/\" && npm install -g @github/copilot",
+  // Start a web server and keep it running
   "postStartCommand": "nohup bash -c 'npm start &'",
-  // Set the port to be public
+  // Set port 4000 to be public
   "postAttachCommand": "gh cs ports visibility 4000:public -c \"$CODESPACE_NAME\"",
-
+  
   // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
   "remoteUser": "node",
 

.github/workflows/create-changelog-pr.yml

@@ -122,7 +122,7 @@ jobs:
             core.setOutput('pull-request-number', pullRequest.number);
             core.setOutput('pull-request-url', pullRequest.html_url);
 
-      - name: Add 'ready-for-doc-review' label to PR
+      - name: Add 'ready-for-doc-review' and 'skip FR board' labels to PR
         if: env.CONTINUE_WORKFLOW == 'true'
         uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd
         env:
@@ -135,7 +135,7 @@ jobs:
               owner: context.repo.owner,
               repo: context.repo.repo,
               issue_number: Number(process.env.PULL_REQUEST_NUMBER),
-              labels: ['ready-for-doc-review']
+              labels: ['ready-for-doc-review','skip FR board']
             });
 
       - name: Assign PR to commenter

.github/workflows/local-dev.yml

@@ -1,9 +1,7 @@
 name: Local development
 
-# **What it does**: Can you start the local server like a writer would do?
-# **Why we have it**: Our CI is often heavily geared on testing in "production"
-#                     that historically we've been known to break local
-#                     development sometimes.
+# **What it does**: Basic smoke test to ensure local dev server starts and serves content
+# **Why we have it**: Catch catastrophic "npm start is completely broken" scenarios
 # **Who does it impact**: Engineers, Contributors.
 
 on:
@@ -28,76 +26,25 @@ jobs:
         with:
           token: ${{ secrets.DOCS_BOT_PAT_BASE }}
 
-      # Note that we don't check out docs-early-access, Elasticsearch,
-      # or any remote translations. Nothing fancy here!
-
       - name: Disable Next.js telemetry
         run: npx next telemetry disable
 
-      - name: Install headless browser
-        run: npx playwright install --no-shell
-
-      # The Playwright test, with the env vars we set here, takes care of
-      # starting a server and shutting it down when it's done.
-      # That's why it's important this step comes before the `npm start &`
-      # step below.
-      - name: Run Playwright tests
-        env:
-          # This is what local dev contributors are expected to do.
-          PLAYWRIGHT_START_SERVER_COMMAND: 'npm start'
-          # This is so that timeouts aren't retried, which can lead to
-          # tests not exiting at the end with a non-zero. Otherwise,
-          # by default failures are marked as "flaky" instead of "failed".
-          PLAYWRIGHT_RETRIES: 0
-          TEST_EARLY_ACCESS: ${{ github.repository == 'github/docs-internal' }}
-          # workaround for https://github.com/nodejs/node/issues/59364 as of 22.18.0
-          NODE_OPTIONS: '--no-experimental-strip-types --max-old-space-size=8192'
-        run: npm run playwright-test -- playwright-local-dev
-
-      - name: Start server in the background
-        run: npm start > /tmp/stdout.log 2> /tmp/stderr.log &
-
-      - name: View the home page
-        run: |
-          echo "Going to sleep a little to wait for the server to start"
-          sleep 10
-          curl --fail --retry-connrefused --retry 5 http://localhost:4000/
-
-      - name: Run basic tests
-        run: npm run test-local-dev
-
-      - if: ${{ failure() }}
-        name: Debug server outputs on errors
+      - name: Start server and basic smoke test
         run: |
-          echo "____STDOUT____"
-          cat /tmp/stdout.log
-          echo "____STDERR____"
-          cat /tmp/stderr.log
-
-      - name: Pre-commit hooks should prevent bad Markdown edits
-        run: |
-          set -e
-
-          # This test assumes this one file always exists
-          ls content/get-started/start-your-journey/hello-world.md
-
-          # Not sure if it matters but we're in a detached HEAD state
-          # after the actions/checkout action.
-          git checkout -b my-new-branch
-          # Also, do this so you don't get errors from git about this
-          # not being set up before your first commit attempt
-          git config user.name github-actions
-          git config user.email github-actions@github.com
-
-          # To know what will fail the markdown lint, see src/content-linter/style/github-docs.js
-          # Add some NOT valid Markdown to it
-          # In this case an internal link with a hardcode /en/ prefix.
-          echo "This *is** not valid [Markdown](/en/foo)" >> content/get-started/start-your-journey/hello-world.md
-          git commit -a -m "this should fail"
-          exit_code=$?
-          if [ $exit_code != 0 ]; then
-            echo "That SHOULD have failed, but it DIDN'T"
-            exit 1
+          # Start server in background
+          npm start > /tmp/stdout.log 2> /tmp/stderr.log &
+          SERVER_PID=$!
+
+          # Wait for server to be ready and test homepage
+          if curl --fail --retry-connrefused --retry 10 --retry-delay 2 http://localhost:4000/; then
+            echo "✅ Local dev server started successfully and serves homepage"
+            kill $SERVER_PID 2>/dev/null || true
           else
-            echo "As expected, it failed :)"
+            echo "❌ Local dev server failed to start or serve content"
+            echo "____STDOUT____"
+            cat /tmp/stdout.log
+            echo "____STDERR____"
+            cat /tmp/stderr.log
+            kill $SERVER_PID 2>/dev/null || true
+            exit 1
           fi

.github/workflows/stale.yml

@@ -24,7 +24,7 @@ jobs:
       - uses: actions/stale@3a9db7e6a41a89f618792c92c0e97cc736e1b13f # v10.0.0
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
-          stale-pr-message: "It looks as if this pull request has been inactive for 30 days. We want to check in with you to see if you plan to continue working on it. If you do, please add a comment to let us know. If we don't hear from you, we will close this pull request after 14 days."
+          stale-pr-message: "It looks as if this pull request has been inactive for 30 days. We want to check in with you to see if you plan to continue working on it. If you do, please add a comment to let us know. If we don't hear from you, we will close this pull request after 14 days. If the PR has been reviewed by a writer and you think it's ready to merge, drop into [#docs-content](https://github-grid.enterprise.slack.com/archives/C0E9DK082) and ask us to merge it."
           days-before-stale: 30
           days-before-close: 14
           stale-pr-label: 'stale'

CHANGELOG.md

@@ -1,12 +1,58 @@
 # Docs changelog
 
+**25 September 2025**
+
+We've updated the documentation for the GA release of [Copilot Spaces](https://github.com/copilot/spaces). Spaces allow you to organize and centralize content and resources in order to ground Copilot Chat's responses in that context and share knowledge across teams. You can now also access Copilot Spaces in your IDE via the GitHub MCP server. 
+
+See the updated docs: 
+* [About organizing and sharing context with GitHub Copilot Spaces](https://docs.github.com/copilot/concepts/context/spaces)
+* [Creating GitHub Copilot Spaces](https://docs.github.com/copilot/how-tos/provide-context/use-copilot-spaces/create-copilot-spaces)
+* [Using GitHub Copilot Spaces](https://docs.github.com/copilot/how-tos/provide-context/use-copilot-spaces/use-copilot-spaces)
+
+<hr>
+
+**24 September 2025**
+
+Until now, assigning Copilot coding agent to an issue was limited to the same repository as the issue. 
+
+You can now: 
+
+* Assign Copilot coding agent to work in a different repository, supporting workflows where issues and code files are managed separately. 
+* Provide additional instructions to tailor the agent's output to your requirements. 
+* Choose the base branch for the agent to use. 
+ 
+These changes provide a more flexible, transparent, and user-friendly experience for managing automated coding tasks with Copilot coding agent. 
+
+See the updated docs: [Using GitHub Copilot to work on an issue](https://docs.github.com/copilot/how-tos/use-copilot-agents/coding-agent/assign-copilot-to-an-issue#assigning-an-issue-to-copilot).
+
+<hr>
+
+**23 September 2025**
+
+We've added new documentation for Spark that answers some common customer questions, helps customers troubleshoot known issues, and guides users on the best ways to prompt and provide context to Spark.
+
+See:
+- [About GitHub Spark](https://docs.github.com/copilot/concepts/spark)
+- [Troubleshooting common issues with GitHub Spark](https://docs.github.com/copilot/how-tos/troubleshoot-copilot/troubleshoot-spark)
+- [Write effective prompts and provide useful context for Spark](https://docs.github.com/copilot/tutorials/spark/prompt-tips)
+
+<hr>
+
+**17 September 2025**
+
+We've added information about the GitHub MCP Registry, and guidance on how to use it in VS Code.
+
+See [About the GitHub MCP Registry](https://docs.github.com/copilot/concepts/context/mcp#about-the-github-mcp-registry) and [Using the GitHub MCP Registry](https://docs.github.com/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp#using-the-github-mcp-registry).
+
+<hr>
+
 **17 September 2025**
 
-We added documentation for expanded features for reusing workflow configurations in GitHub Actions. 
+We've added documentation for expanded features for reusing workflow configurations in GitHub Actions. 
 
-You can now use YAML anchors and aliases to reuse pieces of content in a workflow. See [YAML anchors and aliases](https://docs.github.com/en/actions/concepts/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases). 
+You can now use YAML anchors and aliases to reuse pieces of content in a workflow. See [YAML anchors and aliases](https://docs.github.com/actions/concepts/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases). 
 
-To keep the content focused on users' job-to-be-done, we simplified the procedures for [creating workflow templates for your organization](https://docs.github.com/en/actions/how-tos/reuse-automations/create-workflow-templates). In addition, we updated reference documentation for workflow templates with details on permissions, repository visibility rules, rules for the metadata file, and examples. See [Workflow templates](https://docs.github.com/en/actions/reference/workflows-and-actions/reusing-workflow-configurations#workflow-templates).
+To keep the content focused on users' job-to-be-done, we simplified the procedures for [creating workflow templates for your organization](https://docs.github.com/actions/how-tos/reuse-automations/create-workflow-templates). In addition, we updated reference documentation for workflow templates with details on permissions, repository visibility rules, rules for the metadata file, and examples. See [Workflow templates](https://docs.github.com/actions/reference/workflows-and-actions/reusing-workflow-configurations#workflow-templates).
 
 <hr>
 
@@ -16,7 +62,7 @@ You can now publish your Spark app as "read-only."
 
 By default, data stored in Spark is shared across all users of the app. You can choose to publish your app as "read-only" if you want to showcase your app to others, but you don't want others to be able to edit or delete any stored data.
 
-We've updated the [Spark documentation](https://docs.github.com/en/copilot/tutorials/build-apps-with-spark) accordingly.
+We've updated the [Spark documentation](https://docs.github.com/copilot/tutorials/build-apps-with-spark) accordingly.
 
 <hr>
 
@@ -32,7 +78,7 @@ See [Responsible use of GitHub Copilot code review](https://docs.github.com/copi
 
 Copilot Chat in VS Code includes a "Manage models" option which allows you to add models from a variety of LLM providers, such as Azure, Anthropic, Google, and xAI. By installing the AI Toolkit for VS Code, you can install even more models from the "Manage models" option. We've updated the documentation to include details of how to use this new feature.
 
-See [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/en/copilot/how-tos/use-ai-models/change-the-chat-model?tool=vscode).
+See [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/copilot/how-tos/use-ai-models/change-the-chat-model?tool=vscode).
 
 <hr>
 
@@ -46,9 +92,9 @@ See [Configuring automatic code review by GitHub Copilot](https://docs.github.co
 
 **8 September 2025**
 
-We've added a tutorial on planning a project with GitHub Copilot, including creating issues and sub-issues: [Planning a project with GitHub Copilot](https://docs.github.com/en/copilot/tutorials/plan-a-project). This tutorial provides step-by-step instructions on leveraging Copilot to plan a project from scratch.
+We've added a tutorial on planning a project with GitHub Copilot, including creating issues and sub-issues: [Planning a project with GitHub Copilot](https://docs.github.com/copilot/tutorials/plan-a-project). This tutorial provides step-by-step instructions on leveraging Copilot to plan a project from scratch.
 
-Additionally, we've updated [Using GitHub Copilot to create issues](https://docs.github.com/en/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues) with instructions to create sub-issues and to work with existing issues.
+Additionally, we've updated [Using GitHub Copilot to create issues](https://docs.github.com/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues) with instructions to create sub-issues and to work with existing issues.
 
 <hr>
 
@@ -66,7 +112,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.
@@ -77,7 +123,7 @@ For example, see: [Adding repository custom instructions for GitHub Copilot](htt
 
 **3 September 2025**
 
-We’ve updated [Choosing your enterprise’s plan for GitHub Copilot](https://docs.github.com/en/copilot/get-started/choose-enterprise-plan) to better highlight the long-term benefits of the Copilot Enterprise (CE) plan. The updated content focuses on the key advantages of CE, such as increased access to premium requests and earlier availability of new models.
+We’ve updated [Choosing your enterprise’s plan for GitHub Copilot](https://docs.github.com/copilot/get-started/choose-enterprise-plan) to better highlight the long-term benefits of the Copilot Enterprise (CE) plan. The updated content focuses on the key advantages of CE, such as increased access to premium requests and earlier availability of new models.
 
 <hr>
 

Dockerfile

@@ -8,7 +8,7 @@
 # ---------------------------------------------------------------
 # To update the sha:
 # https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
-FROM ghcr.io/github/gh-base-image/gh-base-noble:20250911-223345-ge6d335835 AS base
+FROM ghcr.io/github/gh-base-image/gh-base-noble:20250929-093120-g65a62eb8c AS base
 
 # Install curl for Node install and determining the early access branch
 # Install git for cloning docs-early-access & translations repos