From 5c2f241b9b807ddbebbb772aa2a3595fd8437b62 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 6 Mar 2026 02:37:30 +0000
Subject: [PATCH 1/2] Initial plan


From ac26e9fa85f525b72fa78271d75983b708ab46dd Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 6 Mar 2026 02:40:12 +0000
Subject: [PATCH 2/2] docs: add merge queue note to copilot-setup-steps example

Co-authored-by: jonstacks <6900888+jonstacks@users.noreply.github.com>
---
 .../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 7a2156191b4c..e69beab6736d 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
@@ -76,6 +76,9 @@ jobs:
       # ...
 ```
 
+> [!NOTE]
+> If your repository uses a merge queue, the `push` trigger above will also run when pull requests are added to the merge queue. To prevent this, add `branches-ignore: ['gh-readonly-queue/**']` to the `push` trigger and restrict the `pull_request` trigger to your default branch with `branches: [YOUR-DEFAULT-BRANCH]`. For more information, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue).
+
 In your `copilot-setup-steps.yml` file, you can only customize the following settings of the `copilot-setup-steps` job. If you try to customize other settings, your changes will be ignored.
 
 * `steps` (see above)