From 4d8d5abc3919072be8d55f825277d9e324491bca 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/2] 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 0eae04c49b1d..e580ca89b6d5 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 e659bda31e7e0c671cea1cb290d5734504da43c3 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/2] 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 e580ca89b6d5..022fc4920e74 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: