Update docs-team cross-repo references to technical-content

[Copilot]

GitHub Copilot generated this pull request.

github/docs-team was renamed to github/technical-content; this updates hardcoded references in github/docs so links and workflow automations use the new canonical repo path instead of relying on redirects. Scope includes required files from the sub-issue plus additional in-repo references found during audit.

• Required workflow link updates

  • .github/workflows/review-comment.yml (2)
    • use-a-codespace-to-review.md
    • deploying-pr-to-staging-servers.md
  • .github/workflows/sync-openapi.yml (1)
    • acting-as-the-first-responder.md

• Required content/data updates

  • src/events/components/experiments/content-ab-testing.md (2)
    • analytics/ab-test.md
    • analytics/dashboard-builder/experiment-results.config.ts
  • data/variables/release-phases.yml (1)
    • issue reference comment

• Additional references to the renamed repo found and updated

  • .github/workflows/sme-review-tracking-issue.yml (2) — target repo for created SME tracking issues
  • .github/instructions/instruction-architecture.instructions.md (2) — architecture doc URL + local checkout reference text
  • src/ghes-releases/lib/release-templates/release-steps-0.md (3) — GHES process links and inline repo name
  • src/redirects/lib/version-preference.ts (1) — issue reference in comment
  • src/redirects/middleware/handle-redirects.ts (1) — issue reference in comment
  • src/workflows/measure-instruction-budget.ts (2) — doc/issue references in comment
  • src/versions/tests/version-cookie.ts (1) — issue reference in comment

• Intentionally left unchanged

  • docs-team-metrics identifiers/rule names (e.g., linter rule names, meta tag keys): these are internal taxonomy/metric labels, not repository references.
  • LABELS: weekly sync,docs-team in content/actions/tutorials/manage-your-work/schedule-issue-creation.md: workflow label value, not a repo link/path.

• Representative change pattern

# before
https://github.com/github/docs-team/blob/main/contributing-to-docs/first-responder/acting-as-the-first-responder.md?plain=1#L156

# after
https://github.com/github/technical-content/blob/main/contributing-to-docs/first-responder/acting-as-the-first-responder.md?plain=1#L156

[github-actions]

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

• .github/instructions/instruction-architecture.instructions.md
• .github/workflows/review-comment.yml
• .github/workflows/sme-review-tracking-issue.yml
• .github/workflows/sync-openapi.yml
• src/events/components/experiments/content-ab-testing.md
• src/ghes-releases/lib/release-templates/release-steps-0.md
• src/redirects/lib/version-preference.ts
• src/redirects/middleware/handle-redirects.ts
• src/versions/tests/version-cookie.ts
• src/workflows/measure-instruction-budget.ts

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process.

The complete list of files we can't accept are:

• .devcontainer/**
• .github/**
• data/reusables/rai/**
• Dockerfile*
• src/**
• package*.json
• content/actions/how-tos/security-for-github-actions/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter contentType: rai.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

[Copilot]

Pull request overview

Updates cross-repository references following the rename from github/docs-team to github/technical-content.

Changes:

• Updates documentation and issue links.
• Retargets SME tracking issue creation.
• Updates instruction architecture references.

The external instruction architecture document was inaccessible, so its requirements could not be verified.

Show a summary per file

File	Description
src/workflows/measure-instruction-budget.ts	Updates source references.
src/versions/tests/version-cookie.ts	Updates issue reference.
src/redirects/middleware/handle-redirects.ts	Updates issue reference.
src/redirects/lib/version-preference.ts	Updates issue reference.
src/ghes-releases/lib/release-templates/release-steps-0.md	Updates GHES process links.
src/events/components/experiments/content-ab-testing.md	Updates analytics links.
data/variables/release-phases.yml	Updates issue URL.
.github/workflows/sync-openapi.yml	Updates responder instructions link.
.github/workflows/sme-review-tracking-issue.yml	Retargets generated issues.
.github/workflows/review-comment.yml	Updates review guidance links.
.github/instructions/instruction-architecture.instructions.md	Updates architecture references.

Review details

Tip

Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 11/11 changed files
• Comments generated: 0
• Review effort level: Balanced