Merge pull request #43313 from github/repo-sync

Repo sync

Author: docs-bot

.github/workflows/content-pipelines.yml

@@ -181,7 +181,7 @@ jobs:
               --body "$PR_BODY" \
               --base main \
               --head "$UPDATE_BRANCH" \
-              --label "workflow-generated,content-pipeline-update,ready-for-doc-review"
+              --label "workflow-generated,content-pipeline-update,ready-for-doc-review,skip FR board"
           fi
 
       - uses: ./.github/actions/slack-alert

content/admin/managing-your-enterprise-account/changing-the-url-for-your-enterprise.md

@@ -16,6 +16,7 @@ If your company pays for {% data variables.product.prodname_ghe_cloud %} by cred
 
 > [!NOTE]
 > If you pay for {% data variables.product.prodname_ghe_cloud %} via invoice, or if your enterprise uses {% data variables.product.prodname_emus %}, you must contact {% data variables.contact.contact_enterprise_sales %} to change your enterprise slug.
+> For enterprises hosted on {% data variables.enterprise.data_residency_site %}, changing the enterprise slug is not currently supported.
 
 ## Considerations when changing your enterprise slug
 

content/code-security/concepts/supply-chain-security/about-dependabot-on-github-actions-runners.md

@@ -43,6 +43,16 @@ Running {% data variables.product.prodname_dependabot %} on standard {% data var
 
 {% data reusables.dependabot.vnet-arc-note %}
 
+## How runner settings interact
+
+The {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_actions %} runners and {% data variables.product.prodname_dependabot %} on self-hosted runners settings are interdependent:
+
+* Enabling "{% data variables.product.prodname_dependabot %} on self-hosted runners" automatically enables "{% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_actions %} runners". Disabling "{% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_actions %} runners" automatically disables "{% data variables.product.prodname_dependabot %} on self-hosted runners".
+* When both settings are enabled, {% data variables.product.prodname_dependabot %} jobs run **only** on self-hosted runners or {% data variables.actions.hosted_runners %} with a `dependabot` label—not on standard {% data variables.product.prodname_dotcom %}-hosted runners.
+
+> [!WARNING]
+> If both settings are enabled but no self-hosted runners or {% data variables.actions.hosted_runners %} with a `dependabot` label are available, {% data variables.product.prodname_dependabot %} jobs will remain queued indefinitely. Ensure runners with this label are configured before enabling "{% data variables.product.prodname_dependabot %} on self-hosted runners".
+
 ## Access and permissions
 
 If you are transitioning to using {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_actions %} runners and you restrict access to your organization's or repository's private resources, you may need to update your list of allowed IP addresses. For example, if you currently limit access to your private resources to the IP addresses that {% data variables.product.prodname_dependabot %} uses, you should update your allowlist to use the {% data variables.product.prodname_dotcom %}-hosted runners IP addresses sourced from the meta API endpoint. For more information, see [AUTOTITLE](/rest/meta).

content/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-on-self-hosted-runners.md

@@ -36,6 +36,9 @@ contentType: how-tos
 
 ## Enabling self-hosted runners for {% data variables.product.prodname_dependabot_updates %}
 
+> [!WARNING]
+> Before enabling "{% data variables.product.prodname_dependabot %} on self-hosted runners", ensure that your self-hosted runners or {% data variables.actions.hosted_runners %} are configured with the runner label used by {% data variables.product.prodname_dependabot %} (by default, `dependabot`). When this setting is enabled, {% data variables.product.prodname_dependabot %} jobs will only run on runners with this label. If no runners with this label are available, jobs will remain queued indefinitely. See [AUTOTITLE](/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners#how-runner-settings-interact).
+
 Once you have configured self-hosted runners for {% data variables.product.prodname_dependabot_updates %}, you can enable or disable {% data variables.product.prodname_dependabot_updates %} on self-hosted runners at the organization or repository level.
 
 > [!NOTE]

content/copilot/concepts/agents/copilot-cli/about-copilot-cli.md

@@ -49,7 +49,7 @@ You can also pass the CLI a single prompt directly on the command line. The CLI
 To use the CLI programmatically, include the `-p` or `--prompt` command-line option in your command. To allow {% data variables.product.prodname_copilot_short %} to modify and execute files you should also use one of the approval options described later in this article—see [Allowing tools to be used without manual approval](#allowing-tools-to-be-used-without-manual-approval) ). For example:
 
   ```bash copy
-  copilot -p "Show me this week's commits and summarize them" --allow-tool 'shell(git)'
+  copilot -p "Show me this week's commits and summarize them" --allow-tool='shell(git)'
   ```
 
   Alternatively, you can use a script to output command-line options and pipe this to `copilot`. For example:
@@ -245,22 +245,22 @@ The `--deny-tool` and `--allow-tool` options require one of the following argume
   For `git` and `gh` commands, you can specify a particular first-level subcommand to allow or deny. For example:
 
   ```shell
-  copilot --deny-tool 'shell(git push)'
+  copilot --deny-tool='shell(git push)'
   ```
 
-  The tool specification is optional. For example, `copilot --allow-tool 'shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
+  The tool specification is optional. For example, `copilot --allow-tool='shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
 
 * `'write'`
 
   This argument allows or denies tools—other than shell commands—permission to modify files.
 
-  For example, `copilot --allow-tool 'write'` allows {% data variables.product.prodname_copilot_short %} to edit files without your individual approval.
+  For example, `copilot --allow-tool='write'` allows {% data variables.product.prodname_copilot_short %} to edit files without your individual approval.
 
 * `'MCP_SERVER_NAME'`
 
   This argument allows or denies tools from the specified MCP server, where `MCP_SERVER_NAME` is the name of an MCP server that you have configured. Tools from the server are specified in parentheses, using the tool name that is registered with the MCP server. Using the server name without specifying a tool allows or denies all tools from that server.
 
-  For example, `copilot --deny-tool 'My-MCP-Server(tool_name)'` prevents {% data variables.product.prodname_copilot_short %} from using the tool called `tool_name` from the MCP server called `My-MCP-Server`.
+  For example, `copilot --deny-tool='My-MCP-Server(tool_name)'` prevents {% data variables.product.prodname_copilot_short %} from using the tool called `tool_name` from the MCP server called `My-MCP-Server`.
 
   You can find an MCP server's name by entering `/mcp` in the CLI's interactive interface, then selecting the server from the list that's displayed.
 
@@ -271,13 +271,13 @@ You can use a combination of approval options to determine exactly which tools {
 For example, to prevent {% data variables.product.prodname_copilot_short %} from using the `rm` and `git push` commands, but automatically allow all other tools, use:
 
 ```shell
-copilot --allow-all-tools --deny-tool 'shell(rm)' --deny-tool 'shell(git push)'
+copilot --allow-all-tools --deny-tool='shell(rm)' --deny-tool='shell(git push)'
 ```
 
 To prevent {% data variables.product.prodname_copilot_short %} from using the tool `tool_name` from the MCP server named `My-MCP-Server`, but allow all other tools from that server to be used without individual approval, use:
 
 ```shell
-copilot --allow-tool 'My-MCP-Server' --deny-tool 'My-MCP-Server(tool_name)'
+copilot --allow-tool='My-MCP-Server' --deny-tool='My-MCP-Server(tool_name)'
 ```
 
 #### Security implications of automatic tool approval

content/copilot/how-tos/copilot-cli/cli-best-practices.md

@@ -76,7 +76,7 @@ To reset previously approved tools, use:
 You can also preconfigure allowed tools via CLI flags:
 
 ```bash
-copilot --allow-tool 'shell(git:*)' --deny-tool 'shell(git push)'
+copilot --allow-tool='shell(git:*)' --deny-tool='shell(git push)'
 ```
 
 **Common permission patterns:**

content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md

@@ -109,7 +109,7 @@ Use `--deny-tool` to prevent {% data variables.product.prodname_copilot_short %}
 * For example:
 
   ```shell
-  copilot --deny-tool 'shell(git push)'
+  copilot --deny-tool='shell(git push)'
   ```
 
 This option takes precedence over the `--allow-all-tools` and `--allow-tool` options.
@@ -121,7 +121,7 @@ Use `--allow-tool` to allow {% data variables.product.prodname_copilot_short %}
 * For example:
 
   ```shell
-  copilot --allow-tool 'shell'
+  copilot --allow-tool='shell'
   ```
 
 ### Specifying which tool you want to allow or deny
@@ -139,18 +139,18 @@ Use `shell(COMMAND)` to allow or deny a specific shell command.
 * For example, to prevent {% data variables.product.prodname_copilot_short %} from using any `rm` command, use:
 
   ```shell
-  copilot --deny-tool 'shell(rm)'
+  copilot --deny-tool='shell(rm)'
   ```
 
 For `git` and `gh` commands, specify a particular first-level subcommand to allow or deny.
 
 * For example, to prevent {% data variables.product.prodname_copilot_short %} from using `git push`, use:
 
   ```shell
-  copilot --deny-tool 'shell(git push)'
+  copilot --deny-tool='shell(git push)'
   ```
 
-The tool specification is optional. For example, `copilot --allow-tool 'shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
+The tool specification is optional. For example, `copilot --allow-tool='shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
 
 #### Allowing or denying `'write'` tools
 
@@ -159,7 +159,7 @@ Use `'write'` to allow or deny tools—other than shell commands—permission to
 * For example, to allow {% data variables.product.prodname_copilot_short %} to edit files without your individual approval, use:
 
   ```shell
-  copilot --allow-tool 'write'
+  copilot --allow-tool='write'
   ```
 
 #### Allowing or denying MCP server tools
@@ -169,7 +169,7 @@ Use `'MCP_SERVER_NAME'` to allow or deny a specific tool from the specified MCP
 * For example, to prevent {% data variables.product.prodname_copilot_short %} from using the tool called `tool_name` from the MCP server called `My-MCP-Server`, use:
 
   ```shell
-  copilot --deny-tool 'My-MCP-Server(tool_name)'
+  copilot --deny-tool='My-MCP-Server(tool_name)'
   ```
 
 `MCP_SERVER_NAME` is the name of an MCP server that you have configured.
@@ -187,13 +187,13 @@ To determine exactly which tools {% data variables.product.prodname_copilot_shor
 * To prevent {% data variables.product.prodname_copilot_short %} from using the `rm` and `git push` commands, but automatically allow all other tools, use:
 
   ```shell
-  copilot --allow-all-tools --deny-tool 'shell(rm)' --deny-tool 'shell(git push)'
+  copilot --allow-all-tools --deny-tool='shell(rm)' --deny-tool='shell(git push)'
   ```
 
 * To prevent {% data variables.product.prodname_copilot_short %} from using the tool `tool_name` from the MCP server named `My-MCP-Server`, but allow all other tools from that server to be used without individual approval, use:
 
   ```shell
-  copilot --allow-tool 'My-MCP-Server' --deny-tool 'My-MCP-Server(tool_name)'
+  copilot --allow-tool='My-MCP-Server' --deny-tool='My-MCP-Server(tool_name)'
   ```
 
 ### Limiting available tools
@@ -246,15 +246,15 @@ To disable URL verification, use the `--allow-all-urls` flag.
 
 ### Pre-approving specific domains
 
-To pre-approve specific domains, use `--allow-url <domain>`.
+To pre-approve specific domains, use `--allow-url=DOMAIN`.
 
-* For example, `--allow-url github.com`.
+* For example, `--allow-url=github.com`.
 
 ### Denying specific domains
 
-To deny specific domains, use `--deny-url <domain>`.
+To deny specific domains, use `--deny-url=DOMAIN`.
 
-* For example, `--deny-url github.com`.
+* For example, `--deny-url=github.com`.
 
 ## Allowing all tools, paths, and URLs
 

content/copilot/how-tos/use-copilot-agents/coding-agent/integrate-coding-agent-with-jira.md

@@ -21,7 +21,9 @@ The {% data variables.product.prodname_copilot %} integration in Jira allows you
 ## Prerequisites
 
 * You must have a {% data variables.product.github %} account with access to {% data variables.product.prodname_copilot_short %} through {% data variables.copilot.copilot_pro_short %}, {% data variables.copilot.copilot_pro_plus_short %}, {% data variables.copilot.copilot_business_short %}, or {% data variables.copilot.copilot_enterprise_short %}.
-* You must have a Jira Cloud account with [AI features enabled](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products).
+* You must have a Jira Cloud account with the following AI features enabled for your organization:
+    * **Jira must be an AI-enabled app** and Rovo must be activated. See [Activate AI for apps](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products) in the Atlassian documentation.
+    * **Beta AI features** must be turned on. See [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation.<!-- markdownlint-disable-line GHD046 -->
 * Installation and authentication must be completed for both Jira and {% data variables.product.github %}.
 
 ## Installation
@@ -77,9 +79,17 @@ The first time you use {% data variables.copilot.copilot_coding_agent %} in Jira
 
 Only users with **write** access to a repository can trigger {% data variables.copilot.copilot_coding_agent %} to work in that repository.
 
+You can trigger {% data variables.copilot.copilot_coding_agent %} in three ways:
+
+* **Assign** {% data variables.product.prodname_copilot %} to a work item using the Assignee field.
+* **Mention** `@{% data variables.product.prodname_copilot %}` in a comment on a work item.
+* **Add {% data variables.product.prodname_copilot_short %} to a workflow transition** so it is triggered automatically when a work item moves to a specific status. See [Collaborate on work items with AI agents](https://support.atlassian.com/jira-software-cloud/docs/collaborate-on-work-items-with-ai-agents/#Add-an-agent-to-workflow-transitions) for setup instructions.
+
 > [!NOTE]
 > When you assign {% data variables.product.prodname_copilot_short %} to a Jira work item, the context the agent captures from Jira will be added to the pull request and **visible to everyone** if the repository is public.
 
+### Example: Triggering {% data variables.copilot.copilot_coding_agent %} from a Jira work item
+
 1. In Jira, open or create a work item that contains clear requirements you want to delegate to {% data variables.copilot.copilot_coding_agent %}.
 1. To specify a repository you want {% data variables.product.prodname_copilot_short %} to work in, mention it in the work item description or in a comment.
 1. Assign `{% data variables.product.prodname_copilot %}` to the work item, or mention `@{% data variables.product.prodname_copilot %}` in a comment. For example:
@@ -109,6 +119,13 @@ For more information, see [AUTOTITLE](/billing/concepts/product-billing/github-c
 
 If you run into problems, try the following solutions.
 
+### You can't see the {% data variables.copilot.copilot_coding_agent %} and it is not possible to assign it to a Jira work item
+
+In Jira, check your Atlassian Administration settings for your organization are set as follows.
+
+1. Jira is an AI-enabled app, see [Activate AI for apps](https://support.atlassian.com/organization-administration/docs/activate-atlassian-intelligence-for-products) in the Atlassian documentation.
+1. Beta AI features are enabled, see [Control access to beta AI features](https://support.atlassian.com/organization-administration/docs/control-access-to-beta-ai-features/) in the Atlassian documentation.<!-- markdownlint-disable-line GHD046 -->
+
 ### You can see the {% data variables.copilot.copilot_coding_agent %} but it is not possible to assign it to a Jira work item
 
 Check that you have connected your personal account on {% data variables.product.github %} to the {% data variables.product.prodname_copilot %} for Jira app.

content/copilot/how-tos/use-copilot-agents/manage-agents.md

@@ -15,7 +15,7 @@ category:
 ## 1. Select a repository and choose your agent
 
 1. Start a new agent task.
-    
+
     * Open the **{% octicon "agent" aria-label="The Agents icon" %} Agents** tab in a repository
     * Open the [Agents page](https://github.com/copilot/agents?ref_product=copilot&ref_type=engagement&ref_style=text)
     * Use the **Task** button or `/task` command from [{% data variables.copilot.copilot_chat_short %}](https://github.com/copilot?ref_product=copilot&ref_type=engagement&ref_style=text)
@@ -40,7 +40,7 @@ For more information on ways to start new agent tasks, see [AUTOTITLE](/copilot/
 
 Once the agent starts working, it will continue to update the session log and overview with its progress and thought process.
 
-Each session displays its status. Click on a session to open the session log, where you can monitor the agent's progress, see the tools it's using, and track how long the session has been running. 
+Each session displays its status. Click on a session to open the session log, where you can monitor the agent's progress, see the tools it's using, and track how long the session has been running.
 
 {% data variables.copilot.copilot_coding_agent %} sessions can also be tracked from the {% data variables.product.prodname_cli %}, {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_vscode %}, Raycast, and JetBrains IDEs. For more information, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/track-copilot-sessions).
 
@@ -68,14 +68,14 @@ In the prompt box under the agent session log, prompt {% data variables.product.
 You can guide the agent in your local development environment on further changes, or make any edits that require human expertise.
 
 ### {% data variables.product.prodname_vscode_shortname %}
-  
+
 At the bottom of the agent session view, click the **{% octicon "vscode" aria-label="VS Code" %} Open in {% data variables.product.prodname_vscode_shortname %}** button to launch the session directly in {% data variables.product.prodname_vscode_shortname %}.
 
 {% data reusables.copilot.coding-agent.use-latest-vscode %}
 
 ### {% data variables.copilot.copilot_cli %}
   1. At the bottom of the agent session view, click the dropdown list next to **{% octicon "vscode" aria-label="VS Code" %} Open in {% data variables.product.prodname_vscode_shortname %}**.
-  1. Click **{% octicon "agent" aria-label="Agent" %} Continue in {% data variables.copilot.copilot_cli %}** to copy the `copilot --resume=<session ID>` command to your clipboard. 
+  1. Click **{% octicon "agent" aria-label="Agent" %} Continue in {% data variables.copilot.copilot_cli %}** to copy the `copilot --resume=SESSION-ID` command to your clipboard.
       ![Screenshot of the session action dropdown list, "Continue in Copilot CLI" is highlighted with a dark orange outline.](/assets/images/help/copilot/coding-agent/open-agent-session-in-copilot-cli.png)
   1. In your terminal, paste and run the command to resume the agent session.
 
@@ -85,7 +85,7 @@ Once the agent completes a session, you can navigate to the pull request to revi
 
 ## 6. Archive agent sessions
 
-Sessions that have been stopped can be archived to remove them from the sessions list. 
+Sessions that have been stopped can be archived to remove them from the sessions list.
 
 1. Open the agent session you want to archive.
 1. In the top right corner, click **{% octicon "kebab-horizontal" aria-label="More actions" %}**, then click **{% octicon "inbox" aria-hidden="true" aria-label="inbox" %} Archive session**.