GitHub Copilot: Comment-Triggered Automations
GitHub CopilotGitHub Copilot's cloud agent automations can now be triggered by comments left on issues or pull requests, expanding beyond the existing schedule- and event-based triggers. Developers configure specific trigger text in the Agents tab's Automations settings, so a matching comment automatically kicks off tasks like refreshing documentation after a code change, investigating an error log, or spinning up a follow-up refactor from a review comment. The feature is available to Copilot Pro, Pro+, Max, Business, and Enterprise subscribers, with Business and Enterprise users needing their administrator to enable the cloud agent policy first.
Key Takeaways
- Comments become a new automation trigger, joining GitHub Copilot's existing schedule- and event-based automation options.
- Maintainers define custom trigger text in the Agents tab's Automations settings to control exactly which comments fire an automation.
- Common use cases include auto-refreshing documentation, investigating error logs from issue comments, and spinning up refactor tasks from review feedback.
- The trigger fires automatically once a matching comment appears, without requiring an explicit @copilot mention.
- The feature is available to Copilot Pro, Pro+, Max, Business, and Enterprise subscribers.
- Business and Enterprise admins must enable the cloud agent policy before their teams can use comment-triggered automations.
Comments as Triggers
GitHub has expanded Copilot cloud agent automations to fire off tasks in response to comments left on issues or pull requests, adding a new trigger type alongside the existing schedule-based and event-based options. Rather than only running on a fixed interval or when an issue is opened, automations can now watch for a specific piece of trigger text inside a comment and kick off a Copilot cloud agent task the moment that text appears.
What It Unlocks
The comment trigger opens up a set of workflows that were previously awkward to automate. A comment left on a code change can automatically prompt Copilot to regenerate or refresh related documentation. A comment on an issue containing an error log or stack trace can trigger an investigation task, with Copilot digging into the root cause before a human even picks up the thread. And a review comment flagging technical debt or a needed refactor can spin up a dedicated follow-up task without anyone having to manually assign it. In each case, the comment itself becomes the action that sets Copilot in motion, rather than requiring someone to separately open an issue or explicitly mention @copilot.
Setting It Up
Automations live in a repository's Agents tab, under the Automations section, where maintainers can now define the exact trigger text that should activate a comment-based automation. Once configured, any comment on an issue or pull request that matches the trigger text fires the automation automatically.
Availability
Comment-triggered automations are rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise subscribers. Business and Enterprise users need their administrator to have enabled the cloud agent policy before the automation can run.