Skip to content

Example automations

Each recipe lists the settings and sample Instructions. Change the text to fit your team, then create the automation. For a weekly security scan, turn on the Weekly Security Scanner in Automations.

  • Trigger: Pull Request / Check Failure, with Job Name equals test
  • Capabilities: Push commit, Post Comment
  • Scope: Selected repositories

Rerunning your tests before devlo pushes needs Startup or higher.

A check failed on this pull request. Find the cause in the code, fix it, and push a commit. Then comment with what you changed. If you can't fix it, explain why.
  • Trigger: Issue / New Issue
  • Capabilities: Update Labels, Assign Issue, Post Comment
  • Scope: All repositories
Read the issue. Add the labels that fit (bug, feature, question). Assign the person who owns the affected area. Post a short comment asking for missing details.
  • Trigger: Pull Request / New Comment, with Comment Body contains /fix
  • Capabilities: Push commit, Post Comment
  • Scope: All repositories
Read the comment that triggered you and fix what it asks for on this pull request's branch. Push one commit and keep the change small. Then reply with what you changed, or why you couldn't.

Daily repository summary by email Paid plans

Section titled “Daily repository summary by email ”
  • Trigger: Schedule / Daily
  • Capabilities: Send Email, with your address as the recipient
  • Scope: Selected repositories, with one repository

Each repository in scope sends its own email.

Summarize what merged, what is waiting for review, and what looks stuck in the last day. Keep it under 200 words.

Also known as: recipes, templates, security scan, fix CI, triage issues, daily summary, /fix.