@@ -91,6 +91,7 @@ jobs:
           fi
 
       - name: Run content pipeline update script
+        id: update
         env:
           GH_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -133,27 +134,48 @@ jobs:
           GH_TOKEN: ${{ secrets.DOCS_BOT_PAT_BASE }}
           UPDATE_BRANCH: ${{ steps.branch.outputs.update_branch }}
           PIPELINE_ID: ${{ matrix.id }}
+          COMPARE_URL: ${{ steps.update.outputs.compare_url }}
+          SHORT_RANGE: ${{ steps.update.outputs.short_range }}
         run: |
           PR_NUMBER="${{ steps.check-pr.outputs.pr_number }}"
           PR_TITLE="docs: update ${PIPELINE_ID} content from source docs"
-
-          PR_BODY="_GitHub Copilot generated this pull request._"$'\n\n'
-          PR_BODY+="> [!NOTE]"$'\n'
-          PR_BODY+="> This PR is **automatically generated** by the [content pipeline update workflow](${{ github.server_url }}/${{ github.repository }}/actions/workflows/content-pipelines.yml). Each run adds a new commit with any documentation changes detected."$'\n\n'
-          PR_BODY+="## What this does"$'\n\n'
-          PR_BODY+="Runs the \`content-pipeline-update\` agent (${PIPELINE_ID}) against the latest source docs and updates official articles under \`content/\` that have fallen out of sync."$'\n\n'
-          PR_BODY+="## Review"$'\n\n'
-          PR_BODY+="* Review each commit for accuracy — the agent uses AI, so spot-check important changes"$'\n'
-          PR_BODY+="* To adjust agent behavior, see [Modifying results](${{ github.server_url }}/${{ github.repository }}/blob/main/src/content-pipelines/README.md#modifying-results)"$'\n'
-          PR_BODY+="* Once satisfied, merge to keep docs up to date"$'\n'
-          PR_BODY+="* A new PR will be created on the next run if there are further changes"
+          NEW_ITEM="* [\`${SHORT_RANGE}\`](${COMPARE_URL})"
 
           if [ -n "$PR_NUMBER" ]; then
-            echo "PR #$PR_NUMBER already exists — new commit pushed"
+            echo "PR #$PR_NUMBER already exists — appending source changes to body"
+
+            EXISTING_BODY=$(gh pr view "$PR_NUMBER" --json body --jq '.body')
+
+            # Append a new bullet before the SOURCE_CHANGES end marker
+            # Uses bash parameter expansion for safe literal string replacement
+            MARKER="<!-- /SOURCE_CHANGES -->"
+            INSERTION="${NEW_ITEM}"$'\n'
+            INSERTION+="${MARKER}"
+            UPDATED_BODY="${EXISTING_BODY/$MARKER/$INSERTION}"
+
+            gh pr edit "$PR_NUMBER" --body "$UPDATED_BODY"
+
             echo "Ensuring PR #$PR_NUMBER is marked ready for review"
             gh pr ready "$PR_NUMBER" || echo "Unable to mark PR #$PR_NUMBER as ready (it may already be ready)"
           else
             echo "Creating new PR"
+
+            PR_BODY="_GitHub Copilot generated this pull request._"$'\n\n'
+            PR_BODY+="> [!NOTE]"$'\n'
+            PR_BODY+="> This PR is **automatically generated** by the [content pipeline update workflow](${{ github.server_url }}/${{ github.repository }}/actions/workflows/content-pipelines.yml). Each run adds a new commit with any documentation changes detected."$'\n\n'
+            PR_BODY+="## What this does"$'\n\n'
+            PR_BODY+="Runs the \`content-pipeline-update\` agent (${PIPELINE_ID}) against the latest source docs and updates official articles under \`content/\` that have fallen out of sync."$'\n\n'
+            PR_BODY+="## Source changes"$'\n\n'
+            PR_BODY+="Changes in the source repo that triggered this update:"$'\n\n'
+            PR_BODY+="<!-- SOURCE_CHANGES -->"$'\n'
+            PR_BODY+="${NEW_ITEM}"$'\n'
+            PR_BODY+="<!-- /SOURCE_CHANGES -->"$'\n\n'
+            PR_BODY+="## Review"$'\n\n'
+            PR_BODY+="* Review each commit for accuracy — the agent uses AI, so spot-check important changes"$'\n'
+            PR_BODY+="* To adjust agent behavior, see [Modifying results](${{ github.server_url }}/${{ github.repository }}/blob/main/src/content-pipelines/README.md#modifying-results)"$'\n'
+            PR_BODY+="* Once satisfied, merge to keep docs up to date"$'\n'
+            PR_BODY+="* A new PR will be created on the next run if there are further changes"
+
             gh pr create \
               --title "$PR_TITLE" \
               --body "$PR_BODY" \
 
@@ -21,6 +21,7 @@ on:
       - 'src/**'
       - '!src/**.json' # So that Docs Engineering isn't reviewing automated pipeline data PRs
       - '!src/**.yml' # So that Docs Engineering isn't reviewing automated pipeline data PRs
+      - '!src/**.sha' # So that Docs Engineering isn't reviewing automated pipeline data PRs
       - '.github/**'
       - 'config/**'
       - '.devcontainer/**'
 
@@ -6,6 +6,8 @@ versions:
 shortTitle: GitHub Command Palette
 redirect_from:
   - /get-started/using-github/github-command-palette
+category:
+  - Customize your experience
 ---
 
 {% data reusables.command-palette.beta-note %}
 
@@ -13,6 +13,8 @@ versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
+category:
+  - Customize your experience
 ---
 ## About keyboard shortcuts
 
 
@@ -12,6 +12,8 @@ redirect_from:
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings
   - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-user-account-settings/managing-your-theme-settings
 shortTitle: Manage theme settings
+category:
+  - Customize your experience
 ---
 
 For choice and flexibility in how and when you use {% data variables.product.github %}, you can configure theme settings to change how {% data variables.product.github %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.github %} to follow your system settings.
 
@@ -9,6 +9,8 @@ versions:
   fpt: '*'
   ghec: '*'
 shortTitle: GitHub Archive program
+category:
+  - Set up your account on GitHub
 ---
 
 {% data reusables.repositories.about-github-archive-program %} For more information, see [AUTOTITLE](/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github#about-the-github-archive-program).
 
@@ -10,6 +10,8 @@ versions:
   fpt: '*'
   ghec: '*'
 shortTitle: Request account archive
+category:
+  - Set up your account on GitHub
 ---
 
 {% data variables.product.github %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through your account settings on {% data variables.product.prodname_dotcom %} or with the User Migration API.
 
@@ -9,6 +9,8 @@ versions:
   ghec: '*'
 redirect_from:
   - /get-started/quickstart/contributing-to-projects
+category:
+  - Explore and contribute
 ---
 
 Contributing to a project on {% data variables.product.github %} is an essential skill for developers and collaborators working together to achieve shared goals. Whether you're fixing bugs, adding features, or improving documentation, the process of contributing ensures structured and efficient collaboration.
 
@@ -6,6 +6,8 @@ versions:
   ghes: '*'
   ghec: '*'
 shortTitle: Contribute to open source
+category:
+  - Explore and contribute
 ---
 
 In this article, you'll learn how to contribute to an open source project by working through an example. We'll guide you through making a contribution to the `github/docs` repository: familiarizing yourself with the repository, finding an area to contribute, making and submitting a pull request, and working with maintainers to get your changes accepted.
 
@@ -15,6 +15,8 @@ versions:
   fpt: '*'
   ghec: '*'
 shortTitle: Finding open source projects
+category:
+  - Explore and contribute
 ---
 
 Open source software powers much of the technology you use daily, from the web browser on your screen to the [NASA Ingenuity helicopter that flew on Mars](https://github.com/readme/featured/nasa-ingenuity-helicopter).