Activate Code Reviewer in your repository
Rovo Dev code review is now Code Reviewer
Rovo Dev code review is now Code Reviewer. Code Reviewer is available with a paid Jira or Teamwork Collection subscription. You don't need a separate Rovo Dev subscription to use it.
With this transition, Code Reviewer uses Rovo credits under our usage-based pricing model. Rovo credit billing won’t start until December 3, 2026.
For more details, read How Code Reviewer uses Rovo credits and what's changing for Rovo Dev.
始める前に
To use Code Reviewer, you need:
A paid Jira or Teamwork Collection subscription.
Bitbucket が DVCS で Jira に接続されていること、または GitHub が GitHub for Jira アプリを使用して Jira に接続されていること。
Turn on Code Reviewer in your Jira site
You need Jira site admin permissions to turn Code Reviewer on or off for a site.
In Jira, select Settings (), then select System.
Under AI & agents, select Developer AI.
Use the toggle to turn Code Reviewer on or off.
On eligible sites, Code Reviewer is on by default, but the triggering schedule is set to “manual”, so Code Reviewer only reviews a pull request when its author asks.
When Code Reviewer is off, it doesn't review pull requests in any repository connected to this site.
Enable Code Reviewer in Bitbucket
Code Reviewer needs to be enabled at the workspace and repository level in Bitbucket.
You need workspace administrator permissions to enable Code Reviewer on a Bitbucket workspace.
To enable Code Reviewer for in a workspace:
In Bitbucket, select Settings () from the top navigation bar, then select Workspace settings.
Under AI, select Code Reviewer.
Select a Jira site (if you have only one Jira site connected, that site will be selected automatically).
Use the toggle to enable Code Reviewer. 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.
Code Reviewer uses Rovo credits from the shared allowance of the organization that the selected Jira site belongs to.
Once you enable Code Reviewer in Bitbucket, choose how Code Reviewer reviews pull requests in your Bitbucket repositories.
Set the review trigger for all repositories
You need workspace administrator permissions to set the default for all repositories in a workspace.
To set the review trigger for all repositories:
Select Settings, and then select Workspace settings.
Under AI, select Code Reviewer.
Choose when Code Reviewer should run: Manual trigger only, Every new pull request, or Every commit.
[既定に設定] を選択する
Repositories use the workspace default unless an admin has changed that repository's own settings.
We recommend setting Review triggers to Every new pull request so new changes are protected.
Change Code Reviewer settings for an individual repository
You need repository administrator permissions to change Code Reviewer settings on a Bitbucket repository.
To change Code Reviewer settings for an individual repository:
Navigate to your repository in Bitbucket, then select Repository settings in the left sidebar.
Under Features, select Code Reviewer.
Turn Code Reviewer on using the AI code reviews in this repository toggle.
Choose when Code Reviewer should run:
Every new pull request: Code Reviewer runs automatically when a pull request is created, but not for subsequent commits.
Every commit: Code Reviewer runs automatically when a pull request is created and whenever a new commit is made.
Manual trigger only: Code Reviewer only runs when the pull request author triggers a review.
To reduce Rovo credit usage, choose Every new pull request or Manual trigger only.
Enable Code Reviewer in GitHub
Code Reviewer needs to be enabled at the organization and repository level for GitHub. You manage GitHub settings in Jira.
To enable Code Reviewer for a GitHub organization:
You need Jira site admin permissions to manage Code Reviewer for a GitHub organization.
In Jira, select Settings (), then select System.
Under AI & agents, select Developer AI.
In the Code Reviewer row, select Manage settings for..., then select GitHub.
Toggle Code Reviewer on for the GitHub organization.
Select Manage organization.
Select a Jira site to start using Code Reviewer.
Code Reviewer uses Rovo credits from the shared allowance of the organization that the this Jira site belongs to.
Once you enable Code Reviewer in Bitbucket, to you can change Code Reviewer settings for a GitHub repository:
You need Jira site admin permissions to change Code Reviewer settings for a repository.
From the organization screen, toggle Code Reviewer on in each repository.
To choose when Code Reviewer should run, select Manage settings for the repository.
Every new pull request: Code Reviewer runs automatically when a pull request is created, but not for subsequent commits.
Every commit: Code Reviewer runs automatically on both pull request creation and every new commit.
Manual trigger only: Code Reviewer only runs when the author comments
@atlassian /reviewon the pull request.
To reduce Rovo credit usage, choose Every new pull request or Manual trigger only.
その他の情報
If your pull request has more than 10,000 lines of changes, or it's in a repository that is larger than 20GB, Code Reviewer may not leave any comments on the pull request (or it might comment that the pull request is too large).
Code Reviewer can review around 10 pull requests in a workspace every minute (depending on system resources).
Each review uses Rovo credits from your organization's shared allowance, and only the author can manually trigger a code review on a pull request. If your organization runs out of Rovo credits, code reviews won't run.
対応言語
Code Reviewer currently supports these languages:
java
javascript
python
C++
Go
ruby
PHP
TypeScript
Kotlin
Swift
ファイルとパターンの除外
To keep reviews focused and reduce noise, Code Reviewer automatically skips some file types:
縮小化されたファイル:
*.min.js、*.min.cssコンパイル済みバイナリおよびバイトコード:
*.exe、*.dll、*.so、*.o、*.a、*.class、*.pyc、*.pyo、*.iso、*.bin、*.dat、*.db、*.mdb、*.sqlite依存関係ロック ファイル:
package-lock.json、yarn.lock、Pipfile.lock、Gemfile.lock、composer.lock(サブディレクトリのバリアントを含む)翻訳ファイル:
*.pot、*.po、*.mo、*.xliff、*.xlfカバレッジ レポート:
*.coverage、coverage.xml、lcov.info、*.lcov、*.gcov、clover.xml、cov.xml、jacoco.xml、jacoco.csv(サブディレクトリのバリアントを含む)テスト スナップショット:
*.snap一般的な静的アセット バイナリ:
画像:
*.png、*.jpg、*.jpeg、*.gif、*.bmp、*.tiff、*.ico、*.svg動画:
*.mp4、*.avi、*.mov、*.wmv、*.flv音声:
*.mp3、*.wav、*.aac、*.ogg、*.flacドキュメント:
*.pdf、*.doc、*.docx、*.ppt、*.pptx、*.xls、*.xlsxアーカイブ:
*.zip、*.rar、*.7z、*.tar、*.gz、*.bz2フォント:
*.ttf、*.otf、*.woff、*.woff2
特別なフォルダー:
.rovodev/**(.rovodevディレクトリ内のすべてのファイル)
Code Reviewer is a premium AI feature that consumes Rovo credits. Find out how Rovo credits work for AI features.
この内容はお役に立ちましたか?