Merge pull request #45986 from github/repo-sync

Repo sync

Author: docs-bot

.github/agents/dependabot-ecosystem-update.md

@@ -23,7 +23,8 @@ There are two ways to get a fix for an alert: agentic autofix and {% data variab
 
 ## Agentic autofix
 
-> [!NOTE] This feature is currently in public preview and is subject to change.
+> [!NOTE]
+> This feature is currently in public preview and is subject to change. {% data reusables.copilot.preview-features-policy %}
 
 Assign a {% data variables.product.prodname_code_scanning %} alert to {% data variables.product.prodname_copilot_short %} to have it resolve the alert for you. Assigning an alert starts an agent session: {% data variables.copilot.copilot_cloud_agent %} calls tools to explore your codebase beyond the affected file, generates a fix, validates it (for example, by re-running {% data variables.product.prodname_codeql %}), and iterates until it opens a pull request with the changes. See [AUTOTITLE](/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/resolve-alerts#fixing-alerts-with-copilot).
 

content/code-security/concepts/code-scanning/autofix-for-code-scanning.md

@@ -36,7 +36,7 @@ With a {% data variables.copilot.copilot_enterprise %} license, you can ask {% d
 ## Fixing alerts with {% data variables.product.prodname_copilot_short %}
 
 > [!NOTE]
-> This feature is in {% data variables.release-phases.public_preview %} and subject to change. {% data variables.copilot.copilot_cloud_agent %} and {% data variables.copilot.copilot_autofix_short %} must be available in the repository.
+> This feature is in {% data variables.release-phases.public_preview %} and subject to change. {% data variables.copilot.copilot_cloud_agent %} and {% data variables.copilot.copilot_autofix_short %} must be available in the repository. {% data reusables.copilot.preview-features-policy %}
 
 You can assign a {% data variables.product.prodname_code_scanning %} alert to {% data variables.product.prodname_copilot_short %} to have it fix the alert for you. Assigning the alert starts an agent session: {% data variables.copilot.copilot_cloud_agent %} explores your codebase, generates a fix, validates it, and opens a pull request.
 

content/code-security/how-tos/manage-security-alerts/manage-code-scanning-alerts/resolve-alerts.md

@@ -134,6 +134,30 @@ Each {% data variables.copilot.copilot_custom_agent_short %} is defined by a Mar
 
   Where `security-auditor` is the file name of the {% data variables.copilot.copilot_custom_agent_short %} profile, without the `.agent.md` extension. Typically, but not necessarily, this is the same as the `name` value in the agent profile.
 
+## Applying your repository's custom instructions to a {% data variables.copilot.copilot_custom_agent_short %}
+
+Custom instruction files—such as `.github/copilot-instructions.md`, `AGENTS.md`, and `CLAUDE.md`—tell {% data variables.product.prodname_copilot_short %} how to work in your repository. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions).
+
+When {% data variables.product.prodname_copilot_short %} runs your {% data variables.copilot.copilot_custom_agent_short %} as a subagent—to handle part of a larger task—the subagent does not follow your repository's custom instructions by default. This keeps the subagent focused on the specific task it was given.
+
+If you want a subagent to follow your repository's conventions—for example, an agent that reviews or edits code—add `include-custom-instructions: true` to the agent file's frontmatter:
+
+```text
+---
+name: RepoAwareReviewer
+description: Reviews a change against this repository's conventions
+tools: ["*"]
+include-custom-instructions: true
+---
+
+Review the change and flag anything that violates the repository's conventions.
+```
+
+> [!NOTE]
+> This setting only affects the agent when it runs as a subagent. A {% data variables.copilot.copilot_custom_agent_short %} that you select yourself—with `--agent`, `/agent`, or by inference—already follows your repository's custom instructions, so the setting has no effect in that case.
+
+For more information, including how this setting interacts with the `--no-custom-instructions` option, see [AUTOTITLE](/copilot/reference/copilot-cli-reference/cli-command-reference#repository-custom-instructions-for-subagents).
+
 ## Further reading
 
 * [AUTOTITLE](/copilot/concepts/agents/copilot-cli/comparing-cli-features)

content/codespaces/the-githubdev-web-based-editor.md

@@ -163,7 +163,7 @@ Most of these commands are available only on the home page of the repository. If
 |`New discussion`|Create a new discussion in the repository. For more information, see [AUTOTITLE](/discussions/quickstart#creating-a-new-discussion).|
 |`New file`|Create a new file from any page in the repository. For more information, see [AUTOTITLE](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository).
 |`New issue`|Open a new issue from any page in the repository. For more information, see [AUTOTITLE](/issues/tracking-your-work-with-issues/using-issues/creating-an-issue).|
-|`Open in {% data variables.codespaces.serverless %} editor`|Open the current repository in the {% data variables.codespaces.serverless %} editor. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-the-githubdev-editor).|
+|`Open in {% data variables.codespaces.serverless %} editor`|Open the current repository in {% data variables.product.prodname_vscode_web %}. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-vs-code-for-the-web-from-github).|
 
 ### File commands
 
@@ -172,7 +172,7 @@ These commands are available only when you open the command palette from a file
 | Command | Behavior|
 | :- | :- |
 |`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see [AUTOTITLE](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit).
-|`Open in {% data variables.codespaces.serverless %} editor`|Open the currently displayed file in {% data variables.codespaces.serverless %} editor. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-the-githubdev-editor).|
+|`Open in {% data variables.codespaces.serverless %} editor`|Open the currently displayed file in {% data variables.product.prodname_vscode_web %}. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-vs-code-for-the-web-from-github).|
 
 ### Discussion commands
 

content/copilot/how-tos/copilot-cli/customize-copilot/create-custom-agents-for-cli.md

@@ -35,7 +35,7 @@ For a tutorial to help you get started with making changes in the browser, see [
 
 Working directly on {% data variables.location.product_location %} is best for small, simple changes, often targeting a single file in a repository. If you want to work in the browser but need to make more complex changes, such as moving content between files, you can choose from the following tools to open a repository in a dedicated editor.
 
-* If you want an editor where you can quickly open or create files, you can press the `.` key in any repository to open the github.dev editor. This is a lightweight web-based editor that includes many of the features of {% data variables.product.prodname_vscode %}, such as a search bar and buttons for Git commands. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor).
+* If you want an editor where you can quickly open or create files, you can press the `.` key in any repository to open {% data variables.product.prodname_vscode_web %}. This is a lightweight web-based editor that includes many of the features of {% data variables.product.prodname_vscode %}, such as a search bar and buttons for Git commands. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor).
 * If you want to stay in the browser but need to do things like run commands, create a test build of your project, or install dependencies, you can open a repository in a codespace. A codespace is a remote development environment with storage and compute power. It includes an editor and integrated terminal, and comes preinstalled with common tools you may need to work with a project, including Git. For more information, see [AUTOTITLE](/codespaces/quickstart).
 
 Alternatively, you can connect to {% data variables.product.github %} from your desktop, and work with a local copy of the repository.{% else %}Working directly in the browser is best for small, simple changes, often targeting a single file in a repository. If you want to make more complex changes, you may need to connect to {% data variables.product.github %} from the desktop, and work with a local copy of the repository.{% endif %}
@@ -68,7 +68,7 @@ For more information about how to authenticate to {% data variables.product.gith
 | ---- | -------- | ------------------ |
 | **On {% data variables.location.product_location %}** | You want a visual interface and need to make quick, simple changes, typically involving a single commit. For an introduction, see [AUTOTITLE](/get-started/using-github/hello-world). | Browser |
 | {% ifversion fpt or ghec %} |
-| **github.dev** | You want to make more complex changes to a repository than is possible on {% data variables.product.prodname_dotcom_the_website %}, but don't need to work with a terminal or tools you have installed on your computer. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-the-githubdev-editor). | Browser |
+| **{% data variables.product.prodname_vscode_web %}** | You want to make more complex changes to a repository than is possible on {% data variables.product.prodname_dotcom_the_website %}, but don't need to work with a terminal or tools you have installed on your computer. For more information, see [AUTOTITLE](/codespaces/the-githubdev-web-based-editor#opening-vs-code-for-the-web-from-github). | Browser |
 | **{% data variables.product.prodname_github_codespaces %}** | You need the resources of a computer to do things like run scripts, create a test build of your project, or install dependencies, and you want to get started quickly by working in a cloud-based environment. For more information, see [AUTOTITLE](/codespaces/quickstart). | Browser or desktop |
 | {% endif %} |
 | **{% data variables.product.prodname_desktop %}** | You want to work with files locally, and would prefer a visual interface to use Git, visualize changes, and interact with {% data variables.product.github %}. For more information, see [AUTOTITLE](/desktop/overview/about-github-desktop). | Desktop |

content/copilot/reference/copilot-cli-reference/cli-command-reference.md

@@ -218,12 +218,6 @@ sections:
         # https://github.com/github/releases/issues/7252
         - |
           Test merge commits for open pull requests are now generated less frequently, improving performance and reducing repository bloat from loose Git objects. The test merge commit associated with a pull request is updated when the pull request itself changes, when the merge base between the two branches changes, or when the current test merge is older than 12 hours. All mergeability checks and rules continue to be honored.
-        # https://github.com/github/releases/issues/6670
-        - |
-          Pull request reviewers can comment on any line of a changed file, not just lines within the diff. Previously, comments could only be placed on the three lines before or after a changed line. This allows reviewers to leave feedback on unchanged lines that need attention and to place comments directly on the relevant line, making review feedback clearer and easier for authors to act on. This feature is in public preview and subject to change.
-        # https://github.com/github/releases/issues/7688
-        - |
-          Users can view PR-level discussion comments in the side panel of the new Files Changed tab, allowing them to follow conversations while reviewing code without switching between the Files Changed and Conversation tabs. The side panel also supports filtering review and discussion comments. This feature is in public preview and subject to change.
 
     - heading: Integrations and extensions
       notes:
@@ -297,3 +291,9 @@ sections:
     # https://github.com/github/releases/issues/6651
     - |
       Closing down: Networking-related syscalls will be disabled by default in the pre-receive hook environment starting in {% data variables.product.prodname_ghe_server %} version 3.22. For enhanced security, hook environments will be placed in dedicated network namespaces. You will be able to override the default setting by setting `pre-receive-hook-networking` to `enabled`. In many cases, [push rulesets](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#push-rulesets) are an alternative for many pre-receive hooks.
+
+  errata:
+    - |
+      These release notes previously included a note about viewing pull request-level discussion comments in the side panel of the new Files Changed tab. The note was added prematurely and has been removed. We will republish it when the feature is ready. [Updated: 2026-09-18]
+    - |
+      These release notes previously included a note about commenting on any line of a changed file in a pull request. The note was added prematurely and has been removed. We will republish it when the feature is ready. [Updated: 2026-09-18]

content/get-started/accessibility/github-command-palette.md

@@ -217,9 +217,6 @@ sections:
         # https://github.com/github/releases/issues/7252
         - |
           Test merge commits for open pull requests are now generated less frequently, improving performance and reducing repository bloat from loose Git objects. The test merge commit associated with a pull request is updated when the pull request itself changes, when the merge base between the two branches changes, or when the current test merge is older than 12 hours. All mergeability checks and rules continue to be honored.
-        # https://github.com/github/releases/issues/7688
-        - |
-          Users can view PR-level discussion comments in the side panel of the new Files Changed tab, allowing them to follow conversations while reviewing code without switching between the Files Changed and Conversation tabs. The side panel also supports filtering review and discussion comments. This feature is in public preview and subject to change.
 
     - heading: Integrations and extensions
       notes:
@@ -300,4 +297,6 @@ sections:
     - |
       These release notes previously included a note about pull request reviewers being able to comment on any line of a changed file, not just lines within the diff. The note was added prematurely and has been removed. We will republish it when the feature is ready. [Updated: 2026-06-23]
     - |
-      These release notes incorrecly indicated that the `case` function is supported in {% data variables.product.prodname_actions %} expressions. [Updated: 2026-07-30]
+      These release notes previously included a note about viewing pull request-level discussion comments in the side panel of the new Files Changed tab. The note was added prematurely and has been removed. We will republish it when the feature is ready.  [Updated: 2026-09-18]
+    - |
+      These release notes incorrectly indicated that the `case` function is supported in {% data variables.product.prodname_actions %} expressions. [Updated: 2026-07-30]