Work with Rovo Dev in automations
This feature is currently in limited beta. Request beta access
Usage during limited beta
During limited beta, Rovo Dev automation actions and triggers don’t use Rovo Dev credits. We’ll notify beta users when this changes.
Beta users are limited to 10 Rovo Dev automation rules per site. We may also limit extremely heavy use of the feature.
Use Rovo Dev actions and triggers in automations to automatically enforce your custom coding standards, or generate code for repetitive tasks at scale so your team can focus on more valuable work.
Rovo Dev automation triggers and actions are most useful for handling coding tasks at scale, or applying and managing organization-level standards across multiple repositories. For single-repository tasks, try Rovo Dev code reviews in Bitbucket and GitHub and Rovo Dev in Jira.
Create an automation rule to review pull requests
To use the Review pull request action, Rovo Dev code reviews must be enabled on your selected repositories.
In your Jira space, select More actions (…) next to your project name, then select Project settings.
In the sidebar, select Automation.
Select Create rule.
Under Add a trigger, search for and select Pull request created (code review).
Select Connect.
Select the repositories you want this rule to apply to, then select Next.
Under Add an action, search for and select Review pull request.
Enter a custom prompt for Rovo Dev to use while reviewing pull requests (e.g. “Check that markdown files start with a single H1, and flag skipped heading levels.” or include specific smart values), then select Next.
Select Turn on rule.
Name your rule, choose who can edit it, then select Turn on rule.
Once the rule is enabled, Rovo Dev will review pull requests in your selected repositories (it may take a few minutes for Rovo Dev to start a review based on an automation rule). Rovo Dev will leave feedback as comments in the pull request.
See which pull requests have triggered your rule in the audit log.
Create an automation rule to generate code
You need administrator permissions to create and manage automation rules.
Define your common coding patterns and use Rovo Dev to automatically generate code for repetitive tasks:
In your Jira space, select More actions (…) next to your space name, then select Space settings.
In the sidebar, select Automation.
Select Create rule.
Under Add a trigger, select a trigger, set it up, then select Next.
Select Add component, then Add an action.
Under Add an action, search for and select Generate code.
Select a connected repository from the list, or select Infer repository from work item if you will add repository details to your work item descriptions.
Select Settings () to configure the branch name and source branch, and whether to create a draft pull request after each automation.
In the Prompt field, give Rovo Dev instructions on the code you want to generate.
Select Next.
Select Turn on rule.
See details on when the rule has triggered and the code generated in the audit log.
Permissions
The generate code action uses the Connection user's permissions. Use this to limit access to repositories and the context Rovo Dev has (like Jira work items, Confluence pages, or pull requests).
Smart values
Use smart values to change the behaviour of rules based specific criteria.
Smart rules can be used in the repository and prompt fields of the generate code action.
For example, using the {{issue.labels}} smart value, you could get Rovo Dev to code in one repository or another based on the work item label.
The generate code action also outputs smart values to use in other automation steps:
Smart value | Description |
|---|---|
| ID of the coding session |
| URL of the repository |
Was this helpful?