Merge pull request #44663 from github/repo-sync

Repo sync

Author: docs-bot

.github/dependabot.yml

@@ -31,6 +31,10 @@ updates:
       day: tuesday
     cooldown:
       default-days: 7
+    groups:
+      actions:
+        patterns:
+          - '*'
     ignore:
       - dependency-name: '*'
         update-types:

.github/workflows/content-pipelines.yml

@@ -161,12 +161,20 @@ jobs:
             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+="> [!WARNING]"$'\n'
+            PR_BODY+="> **Review with care before merging.** The agent generally does a good job, but these PRs can contain:"$'\n'
+            PR_BODY+="> * Information customers don't need to know"$'\n'
+            PR_BODY+="> * Internal or feature-flagged details that shouldn't be public"$'\n'
+            PR_BODY+="> * Excessive or low-value detail"$'\n'
+            PR_BODY+=">"$'\n'
+            PR_BODY+="> Cross-check changes against the source docs linked below. If in doubt, leave the review to a subject-matter expert on the docs team."$'\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+="${SOURCE_LINK}"$'\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+="* Review each commit for accuracy — the agent uses AI, so spot-check important changes against the source docs"$'\n'
+            PR_BODY+="* Watch especially for invented examples, internal-only content, and excessive detail (see warning above)"$'\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"

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

@@ -90,14 +90,22 @@ jobs:
 
           branchname=codeql-cli-update-${{ steps.semmle-code.outputs.OPENAPI_COMMIT_SHA }}
 
-          branchCheckout=$(git checkout -b $branchname)
-          if [[ ! $? -eq 0 ]]; then
-            echo "Branch $branchname already exists in 'github/docs-internal'. Exiting..."
-            exit 0
-          fi
+          git checkout -b $branchname
           git add .
           git commit -m "Update CodeQL CLI data"
-          git push -u origin $branchname
+
+          # Force-push to handle reruns where the branch already exists on the
+          # remote from a prior failed attempt. Plain --force is safe here
+          # because these branches are exclusively managed by this workflow.
+          git push --force -u origin $branchname
+
+          # If a PR already exists for this branch (e.g. a previous run
+          # succeeded but the workflow still reported failure), skip creation.
+          existing_pr=$(gh pr list --repo github/docs-internal --head "$branchname" --json number --jq '.[0].number')
+          if [[ -n "$existing_pr" ]]; then
+            echo "Pull request #$existing_pr already exists for branch $branchname. Skipping PR creation."
+            exit 0
+          fi
 
           echo "Creating pull request..."
           gh pr create \

assets/images/help/copilot/copilot-repo-memory-list.png

@@ -17,14 +17,11 @@ versions:
 children:
   - /managing-security-and-analysis-features
   - /managing-your-tab-size-rendering-preference
-  - /permission-levels-for-a-project-board-owned-by-a-personal-account
   - /manage-cookie-preferences
   - /managing-accessibility-settings
   - /prepare-for-job-change
-  - /managing-access-to-your-personal-accounts-project-boards
   - /integrating-jira-with-your-personal-projects
   - /set-your-hiring-status
 shortTitle: Account settings
 contentType: how-tos
 ---
-

assets/images/help/copilot/copilot-user-memory-list.png

@@ -29,7 +29,5 @@ category:
 
 ## Next steps
 
-{% ifversion projects-v1 %}
-* [AUTOTITLE](/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board){% endif %}
 * [Connect Jira Cloud to GitHub](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html) in the Atlassian documentation
 * For reference information, see [AUTOTITLE](/account-and-profile/reference/personal-account-reference).

content/account-and-profile/how-tos/account-settings/index.md

@@ -428,73 +428,6 @@ on:
   page_build
 ```
 
-{% ifversion projects-v1 %}
-
-## `project`
-
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project`](/webhooks-and-events/webhooks/webhook-events-and-payloads#project) | - `created`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
-
-> [!NOTE]
-> * {% data reusables.developer-site.multiple_activity_types %} The `edited` activity type refers to when a {% data variables.projects.projects_v1_board %}, not a column or card on the {% data variables.projects.projects_v1_board %}, is edited. For information about each activity type, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#project). {% data reusables.developer-site.limit_workflow_to_activity_types %}
-> * {% data reusables.actions.branch-requirement %}
-> * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
-
-Runs your workflow when a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to cards or columns in a {% data variables.projects.projects_v1_board %}, use the [`project_card`](#project_card) or [`project_column`](#project_column) events instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the {% data variables.projects.projects_v1_board %} APIs, see [AUTOTITLE](/graphql/reference/projects-classic#object-project) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic).
-
-For example, you can run a workflow when a project has been `created` or `deleted`.
-
-```yaml
-on:
-  project:
-    types: [created, deleted]
-```
-
-## `project_card`
-
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_card`](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
-
-> [!NOTE]
-> * {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_card). {% data reusables.developer-site.limit_workflow_to_activity_types %}
-> * {% data reusables.actions.branch-requirement %}
-> * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
-
-Runs your workflow when a card on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or columns in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_column`](#project_column) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project card APIs, see [AUTOTITLE](/graphql/reference/projects-classic#object-projectcard) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic/cards).
-
-For example, you can run a workflow when a project card has been `created` or `deleted`.
-
-```yaml
-on:
-  project_card:
-    types: [created, deleted]
-```
-
-## `project_column`
-
-| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
-| --------------------- | -------------- | ------------ | -------------|
-| [`project_column`](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Last commit on default branch | Default branch |
-
-> [!NOTE]
-> * {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see [AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#project_column). {% data reusables.developer-site.limit_workflow_to_activity_types %}
-> * {% data reusables.actions.branch-requirement %}
-> * This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
-
-Runs your workflow when a column on a {% data variables.projects.projects_v1_board %} is created or modified. For activity related to {% data variables.projects.projects_v1_boards %} or cards in a {% data variables.projects.projects_v1_board %}, use the [`project`](#project) or [`project_card`](#project_card) event instead. For more information about {% data variables.projects.projects_v1_boards %}, see [AUTOTITLE](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards). For information about the project column APIs, see [AUTOTITLE](/graphql/reference/projects-classic#object-projectcolumn) in the GraphQL API documentation or [AUTOTITLE](/rest/projects-classic#columns).
-
-For example, you can run a workflow when a project column has been `created` or `deleted`.
-
-```yaml
-on:
-  project_column:
-    types: [created, deleted]
-```
-
-{% endif %}
-
 ## `public`
 
 | Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
@@ -845,7 +778,7 @@ jobs:
 > * The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the API. For information, see [AUTOTITLE](/graphql/reference/commits#object-commit) in the GraphQL API documentation or [AUTOTITLE](/rest/commits#get-a-commit).
 > * Events will not be created if more than 5,000 branches are pushed at once. Events will not be created for tags when more than three tags are pushed at once.
 
-Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs). 
+Runs your workflow when you push a commit or tag, or when you create a repository from a template. This includes workflows that are not merged into the default branch. For more information, see [AUTOTITLE](/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs).
 
 For example, you can run a workflow when the `push` event occurs.