Repo sync

CHANGELOG.md

@@ -1,23 +1,47 @@
 # Docs changelog
 
+**24 September 2025**
+
+Until now, assigning Copilot coding agent to an issue was limited to the same repository as the issue. 
+
+You can now: 
+
+* Assign Copilot coding agent to work in a different repository, supporting workflows where issues and code files are managed separately. 
+* Provide additional instructions to tailor the agent's output to your requirements. 
+* Choose the base branch for the agent to use. 
+
+These changes provide a more flexible, transparent, and user-friendly experience for managing automated coding tasks with Copilot coding agent. 
+
+See the updated docs: [Using GitHub Copilot to work on an issue](https://docs.github.com/copilot/how-tos/use-copilot-agents/coding-agent/assign-copilot-to-an-issue#assigning-an-issue-to-copilot).
+
+<hr>
+
 **23 September 2025**
 
 We've added new documentation for Spark that answers some common customer questions, helps customers troubleshoot known issues, and guides users on the best ways to prompt and provide context to Spark.
 
 See:
-- "[About GitHub Spark](https://docs.github.com/en/copilot/concepts/spark)"
-- "[Troubleshooting common issues with GitHub Spark](https://docs.github.com/en/copilot/how-tos/troubleshoot-copilot/troubleshoot-spark)"
-- "[Write effective prompts and provide useful context for Spark](https://docs.github.com/en/copilot/tutorials/spark/prompt-tips)"
+- [About GitHub Spark](https://docs.github.com/copilot/concepts/spark)
+- [Troubleshooting common issues with GitHub Spark](https://docs.github.com/copilot/how-tos/troubleshoot-copilot/troubleshoot-spark)
+- [Write effective prompts and provide useful context for Spark](https://docs.github.com/copilot/tutorials/spark/prompt-tips)
+
+<hr>
+
+**17 September 2025**
+
+We've added information about the GitHub MCP Registry, and guidance on how to use it in VS Code.
+
+See [About the GitHub MCP Registry](https://docs.github.com/copilot/concepts/context/mcp#about-the-github-mcp-registry) and [Using the GitHub MCP Registry](https://docs.github.com/copilot/how-tos/provide-context/use-mcp/extend-copilot-chat-with-mcp#using-the-github-mcp-registry).
 
 <hr>
 
 **17 September 2025**
 
-We added documentation for expanded features for reusing workflow configurations in GitHub Actions. 
+We've added documentation for expanded features for reusing workflow configurations in GitHub Actions. 
 
-You can now use YAML anchors and aliases to reuse pieces of content in a workflow. See [YAML anchors and aliases](https://docs.github.com/en/actions/concepts/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases). 
+You can now use YAML anchors and aliases to reuse pieces of content in a workflow. See [YAML anchors and aliases](https://docs.github.com/actions/concepts/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases). 
 
-To keep the content focused on users' job-to-be-done, we simplified the procedures for [creating workflow templates for your organization](https://docs.github.com/en/actions/how-tos/reuse-automations/create-workflow-templates). In addition, we updated reference documentation for workflow templates with details on permissions, repository visibility rules, rules for the metadata file, and examples. See [Workflow templates](https://docs.github.com/en/actions/reference/workflows-and-actions/reusing-workflow-configurations#workflow-templates).
+To keep the content focused on users' job-to-be-done, we simplified the procedures for [creating workflow templates for your organization](https://docs.github.com/actions/how-tos/reuse-automations/create-workflow-templates). In addition, we updated reference documentation for workflow templates with details on permissions, repository visibility rules, rules for the metadata file, and examples. See [Workflow templates](https://docs.github.com/actions/reference/workflows-and-actions/reusing-workflow-configurations#workflow-templates).
 
 <hr>
 
@@ -27,7 +51,7 @@ You can now publish your Spark app as "read-only."
 
 By default, data stored in Spark is shared across all users of the app. You can choose to publish your app as "read-only" if you want to showcase your app to others, but you don't want others to be able to edit or delete any stored data.
 
-We've updated the [Spark documentation](https://docs.github.com/en/copilot/tutorials/build-apps-with-spark) accordingly.
+We've updated the [Spark documentation](https://docs.github.com/copilot/tutorials/build-apps-with-spark) accordingly.
 
 <hr>
 
@@ -43,7 +67,7 @@ See [Responsible use of GitHub Copilot code review](https://docs.github.com/copi
 
 Copilot Chat in VS Code includes a "Manage models" option which allows you to add models from a variety of LLM providers, such as Azure, Anthropic, Google, and xAI. By installing the AI Toolkit for VS Code, you can install even more models from the "Manage models" option. We've updated the documentation to include details of how to use this new feature.
 
-See [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/en/copilot/how-tos/use-ai-models/change-the-chat-model?tool=vscode).
+See [Changing the AI model for GitHub Copilot Chat](https://docs.github.com/copilot/how-tos/use-ai-models/change-the-chat-model?tool=vscode).
 
 <hr>
 
@@ -57,9 +81,9 @@ See [Configuring automatic code review by GitHub Copilot](https://docs.github.co
 
 **8 September 2025**
 
-We've added a tutorial on planning a project with GitHub Copilot, including creating issues and sub-issues: [Planning a project with GitHub Copilot](https://docs.github.com/en/copilot/tutorials/plan-a-project). This tutorial provides step-by-step instructions on leveraging Copilot to plan a project from scratch.
+We've added a tutorial on planning a project with GitHub Copilot, including creating issues and sub-issues: [Planning a project with GitHub Copilot](https://docs.github.com/copilot/tutorials/plan-a-project). This tutorial provides step-by-step instructions on leveraging Copilot to plan a project from scratch.
 
-Additionally, we've updated [Using GitHub Copilot to create issues](https://docs.github.com/en/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues) with instructions to create sub-issues and to work with existing issues.
+Additionally, we've updated [Using GitHub Copilot to create issues](https://docs.github.com/copilot/how-tos/use-copilot-for-common-tasks/use-copilot-to-create-issues) with instructions to create sub-issues and to work with existing issues.
 
 <hr>
 
@@ -88,7 +112,7 @@ For example, see: [Adding repository custom instructions for GitHub Copilot](htt
 
 **3 September 2025**
 
-We’ve updated [Choosing your enterprise’s plan for GitHub Copilot](https://docs.github.com/en/copilot/get-started/choose-enterprise-plan) to better highlight the long-term benefits of the Copilot Enterprise (CE) plan. The updated content focuses on the key advantages of CE, such as increased access to premium requests and earlier availability of new models.
+We’ve updated [Choosing your enterprise’s plan for GitHub Copilot](https://docs.github.com/copilot/get-started/choose-enterprise-plan) to better highlight the long-term benefits of the Copilot Enterprise (CE) plan. The updated content focuses on the key advantages of CE, such as increased access to premium requests and earlier availability of new models.
 
 <hr>
 

content/admin/monitoring-and-managing-your-instance/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md

@@ -72,6 +72,9 @@ The time required to failover depends on how long it takes to manually promote t
       {% ifversion ghes > 3.17 %}ghe-repl-decommission UUID{% else %}ghe-repl-teardown -u UUID{% endif %}
       ```
 
+   > [!WARNING]
+   > If you do not intend to re-establish replication from the new primary, you must shut down or delete any appliances that were part of the previous high availability configuration. If those appliances were unreachable during failover, they could cause unintended changes to the new primary if they become reachable later. To prevent configuration conflicts or data integrity issues, always ensure that unused appliances are properly decommissioned.
+
 ## Further reading
 
 * [AUTOTITLE](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#utilities-for-replication-management)

content/copilot/concepts/agents/coding-agent/coding-agent-for-business-and-enterprise.md

@@ -16,6 +16,7 @@ redirect_from:
   - /copilot/concepts/coding-agent/about-enabling-coding-agent
   - /copilot/concepts/coding-agent/enable-coding-agent
   - /copilot/concepts/agents/coding-agent/enable-coding-agent
+  - /copilot/how-tos/agents/copilot-coding-agent/enabling-copilot-coding-agent
 contentType: concepts
 ---
 

content/copilot/how-tos/chat-with-copilot/chat-in-mobile.md

@@ -81,7 +81,7 @@ You can ask a general question about software development{% ifversion ghec %} th
 
 You can ask questions about a specific repository, to get help with understanding the code, or to get help with a specific task you're working on.
 
-1. In {% data variables.product.prodname_mobile %}, navigate to a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="Copilot" %}** icon in the bottom right corner of the screen.
 1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
 
    For example, if you chose the repository you are working in as the context, you could ask:
@@ -132,7 +132,7 @@ You can chat with {% data variables.product.prodname_copilot_short %} about a fi
 
 You can ask questions about a specific pull request in a repository.
 
-1. In {% data variables.product.prodname_mobile %}, navigate to a pull request in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to a pull request in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="Copilot" %}** icon in the bottom right corner of the screen.
 1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
 
    For example, you could ask:
@@ -150,7 +150,7 @@ You can ask questions about a specific pull request in a repository.
 
 You can ask questions about a specific issue in a repository.
 
-1. In {% data variables.product.prodname_mobile %}, navigate to an issue in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to an issue in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="Copilot" %}** icon in the bottom right corner of the screen.
 1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
 
    For example, you could ask:
@@ -168,7 +168,7 @@ You can ask questions about a specific issue in a repository.
 
 You can ask questions about a specific discussion in a repository.
 
-1. In {% data variables.product.prodname_mobile %}, navigate to a discussion in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="copilot" %}** {% data variables.product.prodname_copilot %} icon in the bottom right corner of the screen.
+1. In {% data variables.product.prodname_mobile %}, navigate to a discussion in a repository, and tap the **{% octicon "copilot" aria-hidden="true" aria-label="Copilot" %}** icon in the bottom right corner of the screen.
 1. At the bottom of the page, use the "Ask {% data variables.product.prodname_copilot_short %}" box, type a question and send the message.
 
    For example, you could ask:

content/copilot/how-tos/use-copilot-agents/coding-agent/assign-copilot-to-an-issue.md

@@ -34,11 +34,11 @@ You can ask {% data variables.product.prodname_copilot_short %} to start working
 You can assign an issue to {% data variables.product.prodname_copilot_short %}:
 
 * On {% data variables.product.prodname_dotcom_the_website %} (see the [next section](#assigning-an-issue-to-copilot-on-githubcom))
-* On [{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)
-* Via the {% data variables.product.github %} API (see [later in this article](#assigning-an-issue-to-copilot-via-the-github-api))
+* On [{% data variables.product.prodname_mobile %}](#assigning-an-issue-to-copilot-on-github-mobile)
+* Via the [{% data variables.product.github %} API](#assigning-an-issue-to-copilot-via-the-github-api)
 * Using {% data variables.product.prodname_cli %} (see [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit))
 
-### Assigning an issue to {% data variables.product.prodname_copilot_short %} on {% data variables.product.prodname_dotcom_the_website %}
+## Assigning an issue to {% data variables.product.prodname_copilot_short %} on {% data variables.product.prodname_dotcom_the_website %}
 
 You can assign an issue to {% data variables.product.prodname_copilot_short %} on {% data variables.product.prodname_dotcom_the_website %} in exactly the same way as you assign another user.
 
@@ -77,11 +77,21 @@ You can also assign issues to {% data variables.product.prodname_copilot_short %
 * From the list of issues on a repository's **{% octicon "issue-opened" aria-hidden="true" aria-label="issue-opened" %} Issues** page.
 * When viewing an issue in {% data variables.product.github %} {% data variables.projects.projects_v2_caps %}.
 
-### Assigning an issue to {% data variables.product.prodname_copilot_short %} via the {% data variables.product.github %} API
+## Assigning an issue to {% data variables.product.prodname_copilot_short %} on {% data variables.product.prodname_mobile %}
+
+1. In {% data variables.product.prodname_mobile %}, navigate to the repository that contains the issue you want to assign to {% data variables.product.prodname_copilot_short %}.
+1. Click **Issues**.
+1. Open the issue that you want to assign to {% data variables.product.prodname_copilot_short %}.
+1. Tap the **{% octicon "info" aria-label="information" %}** icon.
+1. Beside "Assignees", tap **Edit**.
+1. Beside "{% data variables.product.prodname_copilot_short %}", click the plus sign.
+1. Click **Done**.
+
+## Assigning an issue to {% data variables.product.prodname_copilot_short %} via the {% data variables.product.github %} API
 
 You can assign issues to {% data variables.product.prodname_copilot_short %} using the GraphQL API.
 
-#### Creating and assigning a new issue
+### Creating and assigning a new issue
 
 1. Make sure you're authenticating with the API using a user token, for example a {% data variables.product.pat_generic %} or a {% data variables.product.prodname_github_app %} user-to-server token.
 1. Verify that {% data variables.copilot.copilot_coding_agent %} is enabled in the repository by checking if the repository's `suggestedActors` in the GraphQL API includes {% data variables.product.prodname_copilot_short %}. Replace `octo-org` with the repository owner, and `octo-repo` with the repository name.
@@ -139,7 +149,7 @@ You can assign issues to {% data variables.product.prodname_copilot_short %} usi
     }
     ```
 
-#### Assigning an existing issue
+### Assigning an existing issue
 
 1. Make sure you're authenticating with the API using a user token, for example a {% data variables.product.pat_generic %} or a {% data variables.product.prodname_github_app %} user-to-server token.
 1. Verify that {% data variables.copilot.copilot_coding_agent %} is enabled in the repository by checking if the repository's `suggestedActors` in the GraphQL API includes {% data variables.product.prodname_copilot_short %}. Replace `octo-org` with the repository owner, and `octo-repo` with the repository name.

content/copilot/how-tos/use-copilot-agents/coding-agent/create-a-pr.md

@@ -100,6 +100,20 @@ You can ask {% data variables.product.prodname_copilot_short %} to open a pull r
 
    {% data variables.product.prodname_copilot_short %} will start a new session and respond with a link to the pull request it creates. It will work on the task and push changes to the pull request, and then add you as a reviewer when it has finished, triggering a notification.
 
+## Asking {% data variables.product.prodname_copilot_short %} to create a pull request from {% data variables.product.prodname_mobile %}
+
+1. In {% data variables.product.prodname_mobile %}, navigate to the repository where you want to create a pull request.
+1. Tap the **{% octicon "copilot" aria-hidden="true" aria-label="Copilot" %}** icon in the bottom right corner of the screen.
+1. Enter a prompt to ask {% data variables.product.prodname_copilot_short %} to create a pull request.
+
+   For example: `Create a pull request to ...`.
+
+   {% data variables.product.prodname_copilot_short %} responds with a brief summary of the task it will perform, asking for your confirmation before it proceeds.
+
+1. Check that {% data variables.product.prodname_copilot_short %} has interpreted your prompt correctly, then tap **Accept** or **Dismiss**.
+
+   {% data variables.product.prodname_copilot_short %} creates a pull request and gives you a link to it. It will work on the task and push changes to the pull request, and then add you as a reviewer when it has finished, triggering a notification.
+
 ## Asking {% data variables.product.prodname_copilot_short %} to create a pull request from the {% data variables.product.prodname_cli %}
 
 > [!NOTE]
@@ -116,13 +130,10 @@ You can use command line options to:
 * Select a repository, instead of targeting the current repository (`--repo`)
 * Follow the session log in real time (`--follow`)
 
-
 To see all of the available options, run `gh agent-task create --help`.
 
 ## Asking {% data variables.product.prodname_copilot_short %} to create a pull request from the {% data variables.product.github %} MCP server
 
-As an alternative to using {% data variables.copilot.copilot_chat_short %}, you can use the remote {% data variables.product.github %} MCP server to trigger {% data variables.copilot.copilot_coding_agent %} from any MCP host.
-
 > [!NOTE]
 > * This capability is only available on the remote {% data variables.product.github %} MCP server and host applications where remote MCP servers are supported.
 

content/copilot/how-tos/use-copilot-agents/coding-agent/track-copilot-sessions.md

@@ -82,6 +82,20 @@ To view the session logs, click on the pull request in the list, then click **Vi
 
 You can also start new agent sessions from {% data variables.product.prodname_vscode %}. See [AUTOTITLE](/copilot/how-tos/agents/copilot-coding-agent/asking-copilot-to-create-a-pull-request#asking-copilot-to-create-a-pull-request-from-copilot-chat-in-visual-studio-code).
 
+## Tracking sessions from {% data variables.product.prodname_mobile %}
+
+You can see a list of your running and past pull requests generated by agents in {% data variables.product.prodname_mobile %}.
+
+1. In the "Agents" section on the {% data variables.product.prodname_mobile %} Home page, tap **Agent Tasks**.
+
+   A list of the currently open pull requests, that you asked {% data variables.product.prodname_copilot_short %} to generate, is displayed.
+
+1. Use the buttons at the top of the list to filter the list of pull requests.
+
+   For example, to show only merged tasks, tap **Open** and then, in the dropdown, tap **Merged**.
+
+   <img width=350rem src="/assets/images/help/copilot/coding-agent/mobile-status-dropdown.png" alt="Screenshot of the status dropdown list with a check mark against 'Open'." />
+
 ## Using the session logs to understand {% data variables.product.prodname_copilot_short %}'s approach
 
 You can dive into {% data variables.product.prodname_copilot_short %}'s session logs in {% data variables.product.github %} or {% data variables.product.prodname_vscode %} to understand how it approached your task.