Enable content pipelines daily run (#59893)

Author: sarahs

.github/workflows/content-pipelines.yml

@@ -14,9 +14,8 @@ name: 'Content pipelines: Update content'
 # values. Run locally: npx tsx src/content-pipelines/scripts/update.ts --help
 
 on:
-  ## COMMENTED OUT FOR TESTING
-  # schedule:
-  #   - cron: "20 16 * * 1-5" # Mon-Fri at 16:20 UTC
+  schedule:
+    - cron: '20 16 * * 1-5' # Mon-Fri at 16:20 UTC
   workflow_dispatch:
 
 permissions:

src/automated-pipelines/README.md

@@ -2,7 +2,7 @@
 
 Our automated pipelines directory contains code shared by our automated pipelines, including REST, GraphQL, Webhooks, CodeQL CLI, and GitHub Apps.
 
-## What is automated pipelines
+## What are automated pipelines
 
 An automated pipeline consumes data from an external source that is used to create content for docs.github.com. An automated pipeline does not automate documentation that is created by our content writing team. For example, if a writer creates a structured data file like YAML or JSON that lives in the `docs-internal` repo, using that data to create a page does not create an automated pipeline.
 

src/content-pipelines/README.md

@@ -1,6 +1,6 @@
 # Content pipelines
 
-Content pipelines is an agent-powered framework for keeping **reference documentation** in sync with source docs that live in external repositories. On a schedule, a workflow clones each external repo, detects whether the source docs have changed, and if they have, runs an AI agent to update our official content articles.
+The content pipelines framework is an agent-powered approach to keeping **reference documentation** in sync with source docs that live in external repositories. On a schedule, a workflow clones each external repo, detects whether the source docs have changed, and if they have, runs an AI agent to update our official content articles.
 
 ## How content pipelines differ from standard automated pipelines