Point docs-engineering references to technical-content (#62866)

Co-authored-by: heiskr <1221423+heiskr@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: d3eeb6ae-47df-4769-a199-cadd3848415d

Author: heiskr

.env.example

@@ -1,11 +1,11 @@
 # This file is a template for what your untracked .env file might look like for local development.
 # Please copy this to a new .env file and fill in the values as needed.
 
-# Requires a running local Elasticsearch service. Can be started via Docker, see https://github.com/github/docs-engineering/blob/main/docs/elasticsearch/elasticsearch-locally.md
+# Requires a running local Elasticsearch service. Can be started via Docker, see https://github.com/github/technical-content/blob/main/engineering/search/elasticsearch-locally.md
 # When this value is unset searches will be proxied to the production Elasticsearch endpoint
 ELASTICSEARCH_URL=http://localhost:9200
 
-# Set for sending events in local development. See https://github.com/github/docs-engineering/blob/main/docs/analytics/hydro-mock.md
+# Set for sending events in local development. See https://github.com/github/technical-content/blob/main/analytics/hydro-mock.md
 HYDRO_ENDPOINT=
 HYDRO_SECRET=
 

.github/actions/create-workflow-failure-issue/action.yml

@@ -1,13 +1,13 @@
 name: Create workflow failure issue
-description: Create or update a GitHub issue in docs-engineering when a workflow fails, for automated diagnosis by an agentic workflow.
+description: Create or update a GitHub issue in technical-content when a workflow fails, for automated diagnosis by an agentic workflow.
 
 inputs:
   token:
     description: A token with issues write permission on the target repo
     required: true
   repo:
     description: The repository to create the issue in
-    default: github/docs-engineering
+    default: github/technical-content
     required: false
 
 outputs:

.github/workflows/benchmark-pages.yml

@@ -18,7 +18,7 @@ jobs:
     runs-on: ubuntu-latest
     env:
       BENCHMARK_LABEL: benchmark-regression
-      ISSUE_REPO: github/docs-engineering
+      ISSUE_REPO: github/technical-content
     steps:
       - name: Checkout
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

.github/workflows/enterprise-dates.yml

@@ -46,7 +46,7 @@ jobs:
           body:
             "Hello! The GitHub Enterprise Server release dates have changed.\n\n
             If CI passes, this PR will be auto-merged. :green_heart:\n\n
-            If CI does not pass or other problems arise, contact #docs-engineering on slack.\n\nThis PR was 🤖-crafted by `.github/workflows/enterprise-dates.yml`. 🧶"
+            If CI does not pass or other problems arise, contact #technical-content on slack.\n\nThis PR was 🤖-crafted by `.github/workflows/enterprise-dates.yml`. 🧶"
           branch: enterprise-server-dates-update
           delete-branch: true
 

.github/workflows/generate-code-scanning-query-lists.yml

@@ -260,7 +260,7 @@ jobs:
             --body '👋 humans. This PR updates the **CodeQL query table reusables** with the latest changes in preparation for the next **CodeQL CLI** release. (Synced from codeql@${{ steps.codeql.outputs.OPENAPI_COMMIT_SHA }})
 
 
-            No action is required from the first responder for the Docs content team. This PR is automatically added to the Docs content review board. Any writer can review this by checking that the PR looks sensible. If CI does not pass or other problems arise, contact #docs-engineering on slack.
+            No action is required from the first responder for the Docs content team. This PR is automatically added to the Docs content review board. Any writer can review this by checking that the PR looks sensible. If CI does not pass or other problems arise, contact #technical-content on slack.
 
 
             When the DRI for the CodeQL CLI release is ready to publish, they will ask us to merge this PR in #docs-content.

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

@@ -305,7 +305,7 @@ jobs:
           # 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 \
+            --repo github/technical-content \
             --label "search-scraping-failures" \
             --state open \
             --limit 200 \
@@ -324,7 +324,7 @@ jobs:
           EOF
           )
             gh issue comment "$existing_issue" \
-              --repo github/docs-engineering \
+              --repo github/technical-content \
               --body "$comment_body"
             exit 0
           fi
@@ -344,7 +344,7 @@ jobs:
           EOF
           )
           gh issue create \
-            --repo github/docs-engineering \
+            --repo github/technical-content \
             --label "search-scraping-failures" \
             --title "[Search Scraping Failures] $today" \
             --body "$body"

.github/workflows/orphaned-features-check.yml

@@ -89,7 +89,7 @@ jobs:
             The first responder should just spot-check some of the orphans
             to make sure they aren't referenced anywhere
             and then approve and merge the pull request.
-            For more information, see [Doc: Orphaned Features](https://github.com/github/docs-engineering/blob/main/docs/orphaned-features.md).
+            For more information, see [Doc: Orphaned Features](https://github.com/github/technical-content/blob/main/engineering/orphaned-features.md).
 
             Generated by the [orphaned features workflow run]($GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID).
           EOM

.github/workflows/orphaned-files-check.yml

@@ -102,7 +102,7 @@ jobs:
 
             If you are the first responder, please spot check some of the unused assets, reusables, and tables to make sure they aren't referenced anywhere. Then, approve and merge the pull request.
 
-            For more information, see [Doc: Orphaned Assets](https://github.com/github/docs-engineering/blob/main/docs/orphaned-assets.md) and [Doc: Reusables CLI](https://github.com/github/docs-internal/tree/main/src/content-render/scripts/reusables-cli).
+            For more information, see [Doc: Orphaned Assets](https://github.com/github/technical-content/blob/main/engineering/orphaned-assets.md) and [Doc: Reusables CLI](https://github.com/github/docs-internal/tree/main/src/content-render/scripts/reusables-cli).
 
             Generated by the [orphaned files workflow run]($GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID).
           EOM

.github/workflows/sync-audit-logs.yml

@@ -88,7 +88,7 @@ jobs:
             --title "Update audit log event data" \
             --body '👋 Docs First Responder. This PR updates the audit log event data with the latest changes, synced from github/audit-log-allowlists.
             Make sure the PR builds successfully and there are no gross errors (for example, a file is deleted). You do not need to validate the contents (that is the responsibility of product teams).
-            If CI does not pass or other problems arise, contact #docs-engineering on slack.' \
+            If CI does not pass or other problems arise, contact #technical-content on slack.' \
             --repo github/docs-internal \
             --label audit-log-pipeline,workflow-generated \
             --head=$branchname

.github/workflows/sync-codeql-cli.yml

@@ -112,7 +112,7 @@ jobs:
 
             This will be reviewed and merged by the Code scanning and GHAS focus team as part of the release of CodeQL CLI. (Synced from semmle-code@${{ steps.semmle-code.outputs.OPENAPI_COMMIT_SHA }})
 
-            If CI does not pass or other problems arise, contact #docs-engineering on slack.' \
+            If CI does not pass or other problems arise, contact #technical-content on slack.' \
             --repo github/docs-internal \
             --label "codeql-cli-pipeline,skip FR board,ready-for-doc-review,workflow-generated"