Radar automation and settings

Radar can automatically review changes whenever a Bubble branch is merged into one of your selected target branches.

Enable automatic scans

You can use different scan settings for each target branch.

1. Open Radar and select Settings.

2. Open Scans.

3. Enable Scan on branch merge.

4. Open Target branches.

5. Select the branches that should trigger a scan.

Only merges into a selected target branch start an automatic scan. A merge into another branch does not.

Configure each branch

Set a stricter review for important branches without applying the same settings everywhere.

1. Expand a branch under Per-branch configuration.

2. Select the scan focuses for that branch.

3. Choose its email or Slack notifications.

4. Save the settings.

For example, you can check bugs, security and maintainability on Test while sending only a product changelog after a merge to Live.

Choose the reviewer

Radar can assign the person who merged the branch as the reviewer.

Set a fallback reviewer for merges where Buildprint cannot match the person who merged to a workspace member. The fallback reviewer also keeps automatic reviews assigned when the original person is unavailable.

Set model priorities

A model priority list gives Radar another model to use when the preferred model is unavailable.

Put your preferred model first, then add fallback models in the order Radar should try them. Each non-Buildprint model needs a connected provider, and Buildprint models need available AI credits.

Send notifications

Notifications tell the right people when an automatic scan finishes.

• Email sends the result to the configured recipients.

• Slack sends a summary to the channel selected for that branch.

Connect your Slack workspace before selecting a channel. Buildprint must have access to the channel used for Radar notifications.

Fix automatic scan problems