A step-by-step guide shows how to use GitHub Copilot app automations to triage Dependabot pull requests automatically. Users create an automation that runs on a schedule (manual, hourly, daily, weekly, or on issue creation), describe the task in natural language (e.g., group PRs by risk, verify CI status, summarize next steps), select a repository, and review results. Automation history is saved for transparency, and Copilot sessions can continue from automation results to handle larger tasks like major version migrations.
Table of contents
Step 1: Create a new automationStep 2: Describe the task in natural languageStep 3: Select the repositoryStep 4: Review the resultsStep 5: Continue the work in a Copilot sessionReview previous automation runsTurn repetitive work into background workTags:Written byQuestions this post answers
How do I set up an automation in the GitHub Copilot app to review Dependabot pull requests automatically?
Create a new automation in the GitHub Copilot app, give it a name like 'Daily Dependabot Triage', and choose a trigger such as daily, hourly, weekly, manual, or on issue creation. Describe the task in natural language, for example asking it to review open Dependabot pull requests, group them by risk, verify CI status, and provide a summary. Then select the target repository and create the automation. daily.dev helps developers stay current on GitHub Copilot workflows like automated dependency triage.
Can GitHub Copilot automations run locally instead of in the cloud?
Yes, GitHub Copilot app automations let you choose whether the automation executes in the cloud or on your local machine, alongside configuring the trigger schedule (manual, hourly, daily, weekly, or issue-based) and the natural language task description. Developers evaluating agentic workflow options can track tooling changes like this via daily.dev.