Good news: your selections are saving on our side, and Bugbot is reviewing PRs on those repos as expected. This is a display issue specific to Azure DevOps, where enabled repos show as disabled (and coverage 0%) after a refresh. You can confirm it’s working by opening a test PR and watching Bugbot leave a review.
One heads-up: since an enabled repo shows as disabled, its toggle will re-send “enable” rather than “disable,” so avoid using the dashboard toggles to turn ADO repos off for now.
We’ve let the team know and it’s an issue we’re tracking. I’ll post here when there’s an update.
In Dashboard > Automations > Bugbot I click the switch to enable Bugbot for one of my Azure DevOps (ADO) repositiories. It turns solid green for a second then turns off again. I went through the first step of enabling Cursor for ADO. Cursor service principle appears in my ADO organization’s Users list. I added the Cursor user as a project admin to my project. My full Repository list correctly appears in the Bugbot dashboard page. The behavior happens on any repo I try to enable. I have “Run for All Authors” turned off and have one engineer specified by email, though I get the same behavior if I turn on Run for All.
Steps to Reproduce
Dashboard > Automations > Bugbot (shows as Enabled) > [select target Organization (all orgs correctly display) ]
On the Bugbot page, click the switch for a Repository.
Switch turns green for a second, then turns off again.
Expected Behavior
Switch should turn green (enabled) and stay that way.
Bugbot should then work on PRs in that repo for the engineer I’ve specified by email address.
