Activate code reviews in your repository

始める前に

To enable Rovo Dev code reviews, you need:

• Rovo Dev on your site.

• Bitbucket connected to Jira by DVCS, or GitHub connected to Jira using the GitHub for Jira app.

Enable code reviews in Bitbucket

Code reviews need to be activated at the workspace and repository level in Bitbucket.

To enable code reviews on a workspace:

1. In Bitbucket, select Settings () from the main navigation, then select Workspace settings.

2. Select Rovo Dev from the left sidebar.

3. Select a Jira site from the dropdown under Rovo Dev credits (if you have only one Jira site connected, that site will be selected automatically).

4. Activate Rovo Dev using the Use Rovo Dev in this workspace toggle.

Rovo Dev credits for code review usage will be deducted from the pull request author’s allocation on the site chosen under Rovo Dev credits.

Then, activate code reviews on the Bitbucket repositories where you want Rovo Dev to review pull requests:

1. Navigate to your repository in Bitbucket, then select Repository settings in the left sidebar.

2. Select Rovo Dev code review in the left sidebar.

3. Activate Rovo Dev code review using the AI code reviews in this repository toggle.

4. Choose when code reviews should run:

   • Only when pull request is created—code reviews run automatically when a pull request is created, but not for subsequent commits.

   • When pull request is created and on each commit—code reviews run automatically when a pull request is created and whenever a new commit is made.

   • Don’t review automatically—code reviews only run when the author manually selects Analyze code in the pull request.

To reduce Rovo Dev credit usage, set code reviews to only run when pull requests are created or triggered manually.

Enable code reviews in GitHub

Code reviews need to be activated at the organization and repository level in GitHub.

To enable code reviews on a GitHub organization:

1. From the app switcher (), select Rovo Dev.

2. From the sidebar, select Settings.

3. Select Manage GitHub settings.

4. Toggle code review on for your organization.

1. Set a Jira site to use Rovo Dev credits for code reviews:

   • To set your current site to be the site used for Rovo Dev credits, select Set billing to this site.

   • To select a different site, switch to that site, repeat steps 1–4, then select Set billing to this site.

Rovo Dev credits for code review usage will be deducted from the pull request author’s allocation on the site chosen under Rovo Dev credits.

Then, to enable code reviews on a GitHub repository:

1. From the organization screen, toggle code reviews on in each repository.

2. To choose when code reviews should run, select Manage settings for the repository.

   • Only when pull request is created—code reviews run automatically when a pull request is created, but not for subsequent commits.

   • When pull request is created and on each commit—code reviews run automatically on both pull request creation and every new commit.

To reduce Rovo Dev credit usage, set code reviews to only run when pull requests are created.

Things you should know

If your pull request has more than 10,000 lines of changes, or it’s in a repository that is larger than 20GB, Rovo Dev may not leave any comments on the pull request (or it might comment that the pull request is too large).

Rovo Dev can review around 10 pull requests in a workspace every minute (depending on system resources).

Rovo Dev credits will be deducted from the pull request author’s allocation, and only the author can manually trigger a code review on a pull request. If the author is out of credits (or doesn’t have an allocation of Rovo Dev credits on the connected Jira site) then code reviews won’t run.

Supported languages

Rovo Dev code review currently supports these languages:

• java

• Javascript

• python

• C++

• Go

• ruby

• PHP

• TypeScript

• Kotlin

• Swift

File and pattern exclusions

To keep code reviews focused and reduce noise, Rovo Dev automatically skips some file types:

• Minified files:
  *.min.js, *.min.css

• Compiled binaries and bytecode:
  *.exe, *.dll, *.so, *.o, *.a, *.class, *.pyc, *.pyo, *.iso, *.bin, *.dat, *.db, *.mdb, *.sqlite

• Dependency lock files:
  package-lock.json, yarn.lock, Pipfile.lock, Gemfile.lock, composer.lock (including any subdirectory variants)

• Translation files:
  *.pot, *.po, *.mo, *.xliff, *.xlf

• Coverage reports:
  *.coverage, coverage.xml, lcov.info, *.lcov, *.gcov, clover.xml, cov.xml, jacoco.xml, jacoco.csv (including any subdirectory variants)

• Test snapshots:
  *.snap

• Common static asset binaries:

  • Images: *.png, *.jpg, *.jpeg, *.gif, *.bmp, *.tiff, *.ico, *.svg

  • Videos: *.mp4, *.avi, *.mov, *.wmv, *.flv

  • Audio: *.mp3, *.wav, *.aac, *.ogg, *.flac

  • Documents: *.pdf, *.doc, *.docx, *.ppt, *.pptx, *.xls, *.xlsx

  • Archives: *.zip, *.rar, *.7z, *.tar, *.gz, *.bz2

  • Fonts: *.ttf, *.otf, *.woff, *.woff2

• Special folders:
  .rovodev/** (all files within the .rovodev directory)