Add copilot to allowed bot users for comment/PR-triggered workflows

[Copilot]

Copilot-authored issue and PR comments were blocked by the bot allowlist in event-driven workflows because copilot[bot] was not included.

Changes

• Added allowed-bot-users: "github-actions[bot],copilot[bot]" to the comment/PR-triggered trigger workflows:
  • .github/workflows/trigger-update-pr-body.yml
  • .github/workflows/trigger-pr-review.yml
  • .github/workflows/trigger-docs-pr-review.yml
  • .github/workflows/trigger-duplicate-issue-detector.yml
  • .github/workflows/trigger-issue-triage.yml
  • .github/workflows/trigger-mention-in-issue.yml
  • .github/workflows/trigger-mention-in-pr.yml
  • .github/workflows/trigger-plan.yml
• Added matching allowed-bot-users dogfood overrides in gh-agent-workflows/*/dogfood-with.yml for the same workflows.
• Scheduled workflows remain unchanged and continue using only github-actions[bot].

Related issue: #320

Generated by Update PR Body

Summary by CodeRabbit

Chores

• Updated automation workflow configurations to recognize additional bot service accounts across documentation reviews, issue detection, PR management, and related automated processes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Adds an allowed-bot-users input/value (mostly "github-actions[bot],copilot") to multiple trigger workflow invocations and the corresponding dogfood-with.yml configurations; no other logic or control-flow changes were introduced.

Changes

Cohort / File(s)	Summary
Trigger workflow invocations .github/workflows/trigger-docs-pr-review.yml, .github/workflows/trigger-duplicate-issue-detector.yml, .github/workflows/trigger-issue-triage.yml, .github/workflows/trigger-mention-in-issue.yml, .github/workflows/trigger-mention-in-pr.yml, .github/workflows/trigger-plan.yml, .github/workflows/trigger-pr-review.yml, .github/workflows/trigger-update-pr-body.yml	Added with: input allowed-bot-users to reusable workflow uses steps; value set to include github-actions[bot] and copilot (minor variation in whether copilot includes [bot]).
Dogfood configuration files gh-agent-workflows/.../dogfood-with.yml (docs-pr-review, duplicate-issue-detector, issue-triage, mention-in-issue, mention-in-pr, plan, pr-review, update-pr-body)	Added top-level allowed-bot-users: "github-actions[bot],copilot" to each dogfood dogfood-with.yml (one file also added edit-style: "high" alongside it).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

• Add Copilot to allowed bot users for automated workflows #320 — Requests adding Copilot to allowed-bot-users across workflows; this PR propagates Copilot into those inputs/configs.

Possibly related PRs

• Add plan workflow templates and docs #323 — Touches the Plan workflow's allowed-bot-users input; closely related to the Plan changes here.
• Add PR Buildkite detective workflow #246 — Also adds/configures allowed-bot-users input across workflow invocations.
• Add configurable allowed-bot-users workflow input #229 — Wires the allowed-bot-users workflow input into reusable gh-aw-* workflows invoked by these trigger files.

Poem

🐰 A tiny hop to widen the crew,
Copilot and Actions join the queue,
Together they nudge each workflow's art,
Paw and bot now play their part,
Hopping forward — builds, deploys, and woo!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The PR fully addresses issue #320 by adding copilot[bot] to allowed bot users in all comment/PR-triggered workflows while preserving scheduled workflows.
Out of Scope Changes check	✅ Passed	All changes are directly related to adding copilot[bot] to allowed bot users across trigger and dogfood configuration files as required by issue #320.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding Copilot to allowed bot users for comment/PR-triggered workflows, which matches the file modifications across all affected workflows.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch copilot/add-copilot-to-allowed-bots

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[strawgate]

@copilot just use copilot not with the bot suffix

[Copilot]

@copilot just use copilot not with the bot suffix

Updated in 1a33f88 — all dogfood-with.yml files and the generated trigger-*.yml files now use copilot without the [bot] suffix.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/ruby/setup-ruby/git/ref/tags/v1
  • Triggering command: /usr/bin/gh gh api /repos/ruby/setup-ruby/git/ref/tags/v1 --jq .object.sha internal/jsonuti. 0.1-go1.25.7.lin--gdwarf2 ux-amd64/pkg/tool/linux_amd64/compile (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)