How coding with devlo works
Describe a change where you already work and devlo makes it on a branch, runs your checks, and opens a pull request. devlo.ai calls this Tickets to PRs.
Where you can ask
Section titled “Where you can ask”| Where | How |
|---|---|
| GitHub issue | Mention @devloai in the issue or a comment |
| Pull request | Mention @devloai in a comment or review thread |
| Jira ticket | Mention @Devlo repo:<name> |
| Slack | Mention @devlo in a channel or direct message |
| devlo app | Start a chat on a repository |
For scheduled or event-triggered runs, use an automation.
What happens
Section titled “What happens”From an issue, Jira, or Slack:
- devlo replies with a status it keeps updated.
- For non-trivial work, it shares a plan first. Mention devlo again to approve it (“go ahead”) or change it.
- It makes the changes on a branch, runs your build and tests, and opens a pull request. devlo never merges; you review and merge it.
- To ask for changes, mention
@devloaion the pull request; devlo pushes to the same branch.
In the app, you follow along and ask for the pull request when you’re ready. devlo can also answer questions about your code instead of changing it.
Good to know
Section titled “Good to know”- Who can start a run depends on where you ask. See Who can trigger devlo.
- Coding works on every plan, including Free. Each run uses your organization’s credits.
- You can’t cancel a run from GitHub, Jira, or Slack. In the app, you can stop a chat.
- By default, devlo doesn’t review the pull requests it opens; comment
/reviewto get one. - Owners and admins see successful runs and their credits in Contribution > Activity.
Next steps
Section titled “Next steps”Also known as: tickets to PRs, tasks, assign devlo, coding agent, issue to PR, ways to ask devlo.