From 9f297826d2e4cbc7c3f6cd44f30fa4ce3b17a89b Mon Sep 17 00:00:00 2001 From: Arthur Date: Mon, 27 Oct 2025 07:59:18 +0000 Subject: [PATCH 1/2] Change initial example to use a specific allowed tool (#58160) --- content/copilot/concepts/agents/about-copilot-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/concepts/agents/about-copilot-cli.md b/content/copilot/concepts/agents/about-copilot-cli.md index 0993b3f450a4..86b83125662f 100644 --- a/content/copilot/concepts/agents/about-copilot-cli.md +++ b/content/copilot/concepts/agents/about-copilot-cli.md @@ -39,7 +39,7 @@ For installation instructions, see [AUTOTITLE](/copilot/how-tos/set-up/install-c * **Programmatic mode**: You can also pass the CLI a single prompt directly on the command line. You do this by using the `-p` or `--prompt` command-line option. To allow {% data variables.product.prodname_copilot_short %} to modify and execute files you should also use one of the approval options (see [Allowing tools to be used without manual approval](#allowing-tools-to-be-used-without-manual-approval) later in this article). For example: ```bash copy - copilot -p "List my open PRs" --allow-all-tools + 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: From 1b0b107b9513dcb5dbb74cfba2606758491cc277 Mon Sep 17 00:00:00 2001 From: Dan Hardej Date: Mon, 27 Oct 2025 16:57:07 +0800 Subject: [PATCH 2/2] Update ARC Quickstart (#58205) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Ben Ahmady <32935794+subatoi@users.noreply.github.com> --- .../tutorials/use-actions-runner-controller/quickstart.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/actions/tutorials/use-actions-runner-controller/quickstart.md b/content/actions/tutorials/use-actions-runner-controller/quickstart.md index a42286cdf1da..dc2a3984e410 100644 --- a/content/actions/tutorials/use-actions-runner-controller/quickstart.md +++ b/content/actions/tutorials/use-actions-runner-controller/quickstart.md @@ -57,6 +57,11 @@ In order to use ARC, ensure you have the following. * Update the `INSTALLATION_NAME` value carefully. You will use the installation name as the value of `runs-on` in your workflows. For more information, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idruns-on). * Update the `NAMESPACE` value to the location you want the runner pods to be created. * Set `GITHUB_CONFIG_URL` to the URL of your repository, organization, or enterprise. This is the entity that the runners will belong to. + {% ifversion fpt %} + * Set `GITHUB_PAT` to a {% data variables.product.company_short %} {% data variables.product.pat_generic %} with the `repo` and `admin:org` scopes for repository and organization runners. + {% else %} + * Set `GITHUB_PAT` to a {% data variables.product.company_short %} {% data variables.product.pat_generic %} with the `repo` and `manage_runners:org` scopes for repository and organization runners, and the `manage_runners:enterprise` scope for enterprise runners. + {% endif %} * This example command installs the latest version of the Helm chart. To install a specific version, you can pass the `--version` argument with the version of the chart you wish to install. You can find the list of releases in the [GitHub Container Registry](https://github.com/actions/actions-runner-controller/pkgs/container/actions-runner-controller-charts%2Fgha-runner-scale-set). > [!NOTE] @@ -134,7 +139,7 @@ Now you will create and run a simple test workflow that uses the runner scale se 1. To view the runner pods being created while the workflow is running, run the following command from your terminal. ```bash copy - kubectl get pods -n arc-runners + kubectl get pods -n arc-runners -w ``` A successful output will look similar to the following.