Merge pull request #39589 from github/repo-sync

Repo sync

Author: docs-bot

content/admin/backing-up-and-restoring-your-instance/backup-service-for-github-enterprise-server/configuring-the-backup-service.md

@@ -62,15 +62,29 @@ If you're using a dedicated block device as your backup target, you need to init
 
     >[!WARNING] This command will permanently erase all data on the specified device. Double-check the device name and back up any important data before proceeding.
 
+    {% ifversion ghes > 3.17 %}
+
+    ```shell
+    ghe-storage-init-backup /dev/YOUR_DEVICE_NAME
+    ```
+
+    {% else %}
+
     ```shell
     /usr/local/share/enterprise/ghe-storage-init-backup /dev/YOUR_DEVICE_NAME
     ```
 
+    {% endif %}
+
     This command:
     * Formats the device (erases all data).
     * Prepares it for use by the backup service.
     * Sets it to mount automatically at `/data/backup` on boot.
 
+    {% ifversion ghes = 3.17 %}
+    From {% data variables.product.prodname_ghe_server %} 3.17.4 onward, the script is installed in PATH so you can run it directly using: `ghe-storage-init-backup /dev/YOUR_DEVICE_NAME`.
+    {% endif %}
+
 #### Reusing a previously initialized disk
 
 If the device was already initialized using `ghe-storage-init-backup`, you can reuse it without reformatting:

content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md

@@ -99,6 +99,10 @@ Your `copilot-setup-steps.yml` file will automatically be run as a normal {% dat
 
 Once you have merged the yml file into your default branch, you can manually run the workflow from the repository's **Actions** tab at any time to check that everything works as expected. For more information, see [AUTOTITLE](/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow).
 
+When {% data variables.product.prodname_copilot_short %} starts work, your setup steps will be run, and updates will show in the session logs. See [AUTOTITLE](/copilot/how-tos/agents/copilot-coding-agent/tracking-copilots-sessions).
+
+If any setup step fails by returning a non-zero exit code, {% data variables.product.prodname_copilot_short %} will skip the remaining setup steps and begin working with the current state of its development environment.
+
 ## Setting environment variables in {% data variables.product.prodname_copilot_short %}'s environment
 
 You may want to set environment variables in {% data variables.product.prodname_copilot_short %}'s environment to configure or authenticate tools or dependencies that it has access to.

content/copilot/how-tos/use-copilot-agents/coding-agent/review-copilot-prs.md

@@ -48,6 +48,8 @@ If {% data variables.product.prodname_copilot_short %} starts a new agent sessio
 > [!TIP]
 > If you don't want {% data variables.product.prodname_copilot_short %} to respond to comments on a pull request, you can unassign {% data variables.product.prodname_copilot_short %} from the pull request. If you later reassign {% data variables.product.prodname_copilot_short %} to the same pull request it will respond to new comments and push more changes. It will not respond to comments that were added while it was not assigned.
 
+As {% data variables.product.prodname_copilot_short %} makes changes to the pull request, it will keep the title and body up to date so they reflect the current changes.
+
 For more information, see the section "Use comments to iterate on a pull request" in [AUTOTITLE](/copilot/tutorials/coding-agent/best-practices#using-comments-to-iterate-on-a-pull-request).
 
 ## Managing {% data variables.product.prodname_actions %} workflow runs

content/copilot/tutorials/coding-agent/get-the-best-results.md

@@ -67,6 +67,8 @@ Working with {% data variables.product.prodname_copilot_short %} on a pull reque
 > [!NOTE]
 > {% data reusables.copilot.coding-agent.write-access-required %}
 
+As {% data variables.product.prodname_copilot_short %} makes changes to the pull request, it will keep the title and body up to date so they reflect the current changes.
+
 ## Adding custom instructions to your repository
 
 By adding custom instructions to your repository, you can guide {% data variables.product.prodname_copilot_short %} on how to understand your project and how to build, test and validate its changes.

package-lock.json

@@ -371,7 +371,7 @@
     "chalk": "^5.0.1",
     "change-case": "^5.4.4",
     "commander": "^14.0.0",
-    "cross-env": "^7.0.3",
+    "cross-env": "^10.0.0",
     "csp-parse": "0.0.2",
     "csv-parse": "6.1.0",
     "eslint": "^8.57.1",

package.json

@@ -1,4 +1,30 @@
 [
+  {
+    "schemaChanges": [
+      {
+        "title": "The GraphQL schema includes these changes:",
+        "changes": [
+          "<p>Type <code>AddBlockedByInput</code> was added</p>",
+          "<p>Type <code>AddBlockedByPayload</code> was added</p>",
+          "<p>Type <code>IssueDependenciesSummary</code> was added</p>",
+          "<p>Type <code>IssueDependencyOrder</code> was added</p>",
+          "<p>Type <code>IssueDependencyOrderField</code> was added</p>",
+          "<p>Type <code>RemoveBlockedByInput</code> was added</p>",
+          "<p>Type <code>RemoveBlockedByPayload</code> was added</p>",
+          "<p>Field <code>blockedBy</code> was added to object type <code>Issue</code></p>",
+          "<p>Field <code>blocking</code> was added to object type <code>Issue</code></p>",
+          "<p>Field <code>issueDependenciesSummary</code> was added to object type <code>Issue</code></p>",
+          "<p>Enum value 'BLOCKED_BY_ADDED_EVENT<code>was added to enum</code>IssueTimelineItemsItemType'</p>",
+          "<p>Field <code>addBlockedBy</code> was added to object type <code>Mutation</code></p>",
+          "<p>Field <code>removeBlockedBy</code> was added to object type <code>Mutation</code></p>",
+          "<p>Enum value 'BLOCKED_BY_ADDED_EVENT<code>was added to enum</code>PullRequestTimelineItemsItemType'</p>"
+        ]
+      }
+    ],
+    "previewChanges": [],
+    "upcomingChanges": [],
+    "date": "2025-07-30"
+  },
   {
     "schemaChanges": [
       {