Merge pull request #44471 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/benchmark-pages.yml

@@ -116,9 +116,9 @@ jobs:
               echo ""
               echo "### Errors"
               echo ""
-              echo "| Status | Mode | Path |"
-              echo "|--------|------|------|"
-              jq -r '.errors[] | "| \(.status) | \(.mode) | \(.path) |"' /tmp/benchmark-results.json
+              echo "| Status | Mode | Path | Error |"
+              echo "|--------|------|------|-------|"
+              jq -r '.errors[] | "| \(.status) | \(.mode) | \(.path) | \(.errorBody // "" | gsub("\\|"; "\\|") | gsub("\r"; " ") | gsub("\n"; " ")) |"' /tmp/benchmark-results.json
             } >> "$BODY_FILE"
           fi
 

.github/workflows/changelog-agent.yml

@@ -321,10 +321,6 @@ jobs:
         with:
           node-version-file: 'package.json'
 
-      - name: Install Copilot CLI
-        if: steps.check_parent.outputs.has_parent == 'true' && steps.check_existing.outputs.exists == 'false'
-        run: npm install -g @github/copilot@prerelease
-
       - name: Prepare prompts for LLM
         if: steps.check_parent.outputs.has_parent == 'true' && steps.check_existing.outputs.exists == 'false'
         id: prepare_prompts

.github/workflows/index-general-search.yml

@@ -294,33 +294,42 @@ jobs:
             echo 'EOF'
           } >> "$GITHUB_OUTPUT"
 
-      - name: Close previous scraping failure issues
+      - name: Comment on or create scraping failure issue
         if: ${{ steps.check-artifacts.outputs.has_artifacts == 'true' && fromJSON(steps.aggregate.outputs.result || '{"hasFailures":false}').hasFailures }}
         env:
           GH_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}
+          FAILURE_MESSAGE: ${{ fromJSON(steps.aggregate.outputs.result || '{"message":""}').message }}
           RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+          FILE_URL: ${{ github.server_url }}/${{ github.repository }}/blob/main/.github/workflows/index-general-search.yml
+          WORKFLOW_NAME: ${{ github.workflow }}
         run: |
-          open_issues=$(gh issue list \
+          # Reuse the oldest open scraping-failures issue if one exists,
+          # to keep the noise down. Otherwise open a new one.
+          existing_issue=$(gh issue list \
             --repo github/docs-engineering \
             --label "search-scraping-failures" \
             --state open \
-            --json number \
-            --jq '.[].number')
-          for issue in $open_issues; do
-            gh issue close "$issue" \
+            --limit 200 \
+            --json number,createdAt \
+            --jq 'sort_by(.createdAt) | .[0].number // empty')
+
+          today=$(date -u +%Y-%m-%d)
+
+          if [ -n "$existing_issue" ]; then
+            comment_body=$(cat <<EOF
+          ### Search index scraping failures ($today)
+
+          $FAILURE_MESSAGE
+
+          **Workflow run:** $RUN_URL
+          EOF
+          )
+            gh issue comment "$existing_issue" \
               --repo github/docs-engineering \
-              --comment "Closing in favor of a newer scraping failure report from $RUN_URL"
-          done
+              --body "$comment_body"
+            exit 0
+          fi
 
-      - name: Create scraping failure issue
-        if: ${{ steps.check-artifacts.outputs.has_artifacts == 'true' && fromJSON(steps.aggregate.outputs.result || '{"hasFailures":false}').hasFailures }}
-        env:
-          GH_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}
-          FAILURE_MESSAGE: ${{ fromJSON(steps.aggregate.outputs.result || '{"message":""}').message }}
-          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
-          FILE_URL: ${{ github.server_url }}/${{ github.repository }}/blob/main/.github/workflows/index-general-search.yml
-          WORKFLOW_NAME: ${{ github.workflow }}
-        run: |
           body=$(cat <<EOF
           ### Search index scraping failures
 
@@ -331,6 +340,8 @@ jobs:
           **Workflow file:** $FILE_URL
 
           This issue was automatically created by the \`$WORKFLOW_NAME\` workflow.
+          Subsequent failures from later workflow runs will be added as comments
+          on this issue rather than opening a new issue each day.
 
           ---
 
@@ -357,16 +368,17 @@ jobs:
              offending/illegal tag token when available.
           3. **Open a pull request that fixes the corruptions** rather than
              just commenting the findings on this issue. The issue body above
-             already lists the affected pages; the value the agent adds is
-             the fix. Where possible, fix the underlying pattern in
+             (and any subsequent comments) already lists the affected pages;
+             the value the agent adds is the fix. Where possible, fix the
+             underlying pattern in
              \`src/languages/lib/correct-translation-content.ts\` so the same
              corruption is corrected on future syncs.
           EOF
           )
           gh issue create \
             --repo github/docs-engineering \
             --label "search-scraping-failures" \
-            --title "[Search Scraping Failures] $(date -u +%Y-%m-%d)" \
+            --title "[Search Scraping Failures] $today" \
             --body "$body"
 
       - name: Send consolidated Slack notification

.github/workflows/test-changed-content.yml

@@ -49,9 +49,16 @@ jobs:
         uses: tj-actions/changed-files@22103cc46bda19c2b464ffe86db46df6922fd323 # v47.0.5
         with:
           files: 'content/**'
+          # Needed to expose `all_old_new_renamed_files` (old,new pairs for renames).
+          # Without this, files git classifies as renames (status R) are invisible to
+          # the deleted-file redirect check below and old URLs can silently 404.
+          include_all_old_new_renamed_files: true
 
       - name: Run tests
         env:
           CHANGED_FILES: ${{ steps.changed_files.outputs.all_modified_files }}
           DELETED_FILES: ${{ steps.changed_files.outputs.deleted_files }}
+          # Space-separated `oldPath,newPath` pairs. The test treats the old paths
+          # like deleted files so missing redirects on renames are caught.
+          RENAMED_FILES: ${{ steps.changed_files.outputs.all_old_new_renamed_files }}
         run: npm test -- src/content-render/tests/render-changed-and-deleted-files.ts

Dockerfile

@@ -114,8 +114,11 @@ RUN npm run warmup-remotejson
 # --------------------------------------
 FROM build AS precompute_stage
 
-# Generate precomputed page info
-RUN npm run precompute-pageinfo -- --max-versions 2
+# Generate precomputed page info. Only English + free-pro-team@latest
+# permalinks are cached; cache misses for older versions and translated
+# pages fall through to runtime compute (which is cheap and Fastly-cached
+# per pathname after the first hit).
+RUN npm run precompute-pageinfo -- --max-versions 1
 
 # -------------------------------------------------
 # PRODUCTION STAGE: What will run on the containers

content/copilot/tutorials/copilot-cli-hooks.md

@@ -374,7 +374,7 @@ REDACTED_TOOL_ARGS="$(echo "$TOOL_ARGS_RAW" | \
   sed -E 's/ghp_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
   sed -E 's/gho_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
   sed -E 's/ghu_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
-  sed -E 's/ghs_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
+  sed -E 's/ghs_[A-Za-z0-9\._\-]{20,}/[REDACTED_TOKEN]/g' | \
   sed -E 's/Bearer [A-Za-z0-9_\-\.]+/Bearer [REDACTED]/g' | \
   sed -E 's/--password[= ][^ ]+/--password=[REDACTED]/g' | \
   sed -E 's/--token[= ][^ ]+/--token=[REDACTED]/g')"
@@ -416,7 +416,7 @@ deny() {
     sed -E 's/ghp_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
     sed -E 's/gho_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
     sed -E 's/ghu_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
-    sed -E 's/ghs_[A-Za-z0-9]{20,}/[REDACTED_TOKEN]/g' | \
+    sed -E 's/ghs_[A-Za-z0-9\.\-_]{20,}/[REDACTED_TOKEN]/g' | \
     sed -E 's/Bearer [A-Za-z0-9_\-\.]+/Bearer [REDACTED]/g' | \
     sed -E 's/--password[= ][^ ]+/--password=[REDACTED]/g' | \
     sed -E 's/--token[= ][^ ]+/--token=[REDACTED]/g')"

content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/export-or-migrate-github-classroom-data.md

@@ -0,0 +1,39 @@
+---
+title: Export or migrate GitHub Classroom data
+intro: 'Export your GitHub Classroom data to local files or migrate your data to a partner platform.'
+versions:
+  fpt: '*'
+---
+
+Use the GitHub command line interface to export your Classroom data or migrate to a partner platform.
+
+## Export your Classroom data to local files
+
+1. Set up the GitHub command line interface (CLI) tool and install the GitHub Classroom extension. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/using-github-classroom-with-github-cli).
+
+1. Download the Classroom Export Utility script to your computer. See the [classroom-export-utility repository](https://github.com/github-education-resources/classroom-export-utility/blob/main/export-classrooms.sh).
+
+1. Follow the instructions in the [Classroom Export Utility README](https://github.com/github-education-resources/classroom-export-utility/blob/main/README.md) to download your Classroom data.
+
+1. Verify that all your classroom data has been exported to JSON or CSV files on your local machine.
+
+## Migrate existing GitHub Classroom data to a partner
+
+### Migrating to Codio
+
+Follow the [instructions on the Codio documentation site](https://docs.codio.com/instructors/setupcourses/import-from-github-classroom.html) and watch the video walkthrough to import your GitHub classrooms to the Codio platform.
+
+You can also book a free consultation to get personalized advice and tips on your classroom setup and migration options at [https://www.codio.com/consultation](https://www.codio.com/consultation).
+
+Watch the [on-demand webinar about using GitHub with Codio](https://www.codio.com/on-demand-github-codio-webinar).
+
+### Migrating to Classroom 50
+
+> [!NOTE]
+> Classroom 50 will become generally available on July 1, 2026.
+
+Classroom 50 uses GitHub repositories and actions for autograding, so it's very similar to the current GitHub Classroom setup.
+
+The [Teacher Guide](https://github.com/foundation50/classroom50/wiki/Teacher-Guide) provides instructions for setting up Classroom 50.
+
+Participate in the [Classroom 50 community discussions](https://github.com/foundation50/classroom50/discussions) if you have questions or suggestions.

content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/index.md

@@ -10,4 +10,5 @@ redirect_from:
 children:
   - /about-github-classroom
   - /glossary
+  - /export-or-migrate-github-classroom-data
 ---

content/education/manage-coursework-with-github-classroom/index.md

@@ -11,3 +11,6 @@ children:
   - /learn-with-github-classroom
 ---
 
+> [!NOTE]
+> As of May 2026, new {% data variables.product.prodname_classroom %} sign-ups are no longer available as we transition to partner solutions. For more information on this transition, please see [the {% data variables.product.prodname_classroom %} transition announcement](https://gh.io/classroom-sunset).
+

content/graphql/overview/rate-limits-and-query-limits-for-the-graphql-api.md

@@ -287,9 +287,11 @@ These two examples show how to calculate the total nodes in a call.
 
 If {% data variables.product.github %} takes more than 10 seconds to process an API request, {% data variables.product.github %} will terminate the request and you will receive a timeout response and a message reporting that "We couldn't respond to your request in time".
 
+When this happens, you may receive either a `502` or `504` status code. Both status codes indicate that your request timed out.
+
 {% data variables.product.github %} reserves the right to change the timeout window to protect the speed and reliability of the API.
 
-You can check the status of the GraphQL API at [githubstatus.com](https://www.githubstatus.com/) to determine whether the timeout is due to a problem with the API. You can also try to simplify your request or try your request later. For example, if you are requesting a large number of objects in a single request, you can try requesting fewer objects split over multiple queries.
+You can check the status of the GraphQL API at [githubstatus.com](https://www.githubstatus.com/) to determine whether the timeout is due to a problem with the API. You can also try to simplify your request or try your request later. For tips on improving query performance, see [Query optimization strategies](#query-optimization-strategies).
 
 If a timeout occurs for any of your API requests, additional points will be deducted from your primary rate limit for the next hour to protect the speed and reliability of the API.