From abd4a6bf2b9d3c0705df8f5deabadaaa4d1e0bbe Mon Sep 17 00:00:00 2001 From: Stephen Finch <57785785+stephenfinch@users.noreply.github.com> Date: Thu, 7 Aug 2025 10:28:14 -0400 Subject: [PATCH 1/3] Update customize-the-agent-environment.md Add note to explain how the setup-steps yml file must live on your default branch for it to be triggered when copilot opens a PR --- .../coding-agent/customize-the-agent-environment.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md index 68a4af034f6a..071280d3dcc6 100644 --- a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md +++ b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md @@ -40,6 +40,9 @@ Instead, you can preconfigure {% data variables.product.prodname_copilot_short % A `copilot-setup-steps.yml` file looks like a normal {% data variables.product.prodname_actions %} workflow file, but must contain a single `copilot-setup-steps` job. This job will be executed in {% data variables.product.prodname_actions %} before {% data variables.product.prodname_copilot_short %} starts working. For more information on {% data variables.product.prodname_actions %} workflow files, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions). +> [!NOTE] +> You must have merged the yml file into your default branch + Here is a simple example of a `copilot-setup-steps.yml` file for a TypeScript project that clones the project, installs Node.js and downloads and caches the project's dependencies. You should customize this to fit your own project's language(s) and dependencies: ```yaml copy From 68ed61d35f6bf70484708464410cced71a95cf72 Mon Sep 17 00:00:00 2001 From: Stephen Finch <57785785+stephenfinch@users.noreply.github.com> Date: Thu, 7 Aug 2025 10:35:35 -0400 Subject: [PATCH 2/3] use copilots wording --- .../coding-agent/customize-the-agent-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md index 071280d3dcc6..31177cba1e1c 100644 --- a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md +++ b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md @@ -41,7 +41,7 @@ Instead, you can preconfigure {% data variables.product.prodname_copilot_short % A `copilot-setup-steps.yml` file looks like a normal {% data variables.product.prodname_actions %} workflow file, but must contain a single `copilot-setup-steps` job. This job will be executed in {% data variables.product.prodname_actions %} before {% data variables.product.prodname_copilot_short %} starts working. For more information on {% data variables.product.prodname_actions %} workflow files, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions). > [!NOTE] -> You must have merged the yml file into your default branch +> You must have merged the yml file into your default branch for it to be triggered Here is a simple example of a `copilot-setup-steps.yml` file for a TypeScript project that clones the project, installs Node.js and downloads and caches the project's dependencies. You should customize this to fit your own project's language(s) and dependencies: From 9de2f77e3db8cba76bb1f6e51fe087f02bdad65e Mon Sep 17 00:00:00 2001 From: Stephen Finch <57785785+stephenfinch@users.noreply.github.com> Date: Fri, 22 Aug 2025 13:35:01 -0400 Subject: [PATCH 3/3] Update content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md Co-authored-by: Sharra-writes --- .../coding-agent/customize-the-agent-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md index 31177cba1e1c..aba270e2dd6a 100644 --- a/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md +++ b/content/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment.md @@ -41,7 +41,7 @@ Instead, you can preconfigure {% data variables.product.prodname_copilot_short % A `copilot-setup-steps.yml` file looks like a normal {% data variables.product.prodname_actions %} workflow file, but must contain a single `copilot-setup-steps` job. This job will be executed in {% data variables.product.prodname_actions %} before {% data variables.product.prodname_copilot_short %} starts working. For more information on {% data variables.product.prodname_actions %} workflow files, see [AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions). > [!NOTE] -> You must have merged the yml file into your default branch for it to be triggered +> The `copilot-setup-steps.yml` workflow won't trigger unless it's present on your main branch. Here is a simple example of a `copilot-setup-steps.yml` file for a TypeScript project that clones the project, installs Node.js and downloads and caches the project's dependencies. You should customize this to fit your own project's language(s) and dependencies: