BugBot re-reviewing PRs on push despite being configured to only run once

I have configured BugBot to only review PRs once but it is re-running every time we push to open PRs. This doesn’t seem right, can anyone confirm? We’re in free trial at the moment but don’t want a massive cost when our trial finishes. Our ideal workflow is that it runs once when PRs are raised and then if any changes are pushed that we feel warrant a re-review from BugBot we’ll comment to manually re-trigger.

This is our config:

This is an example PR where it has now run 3 times despite config being set to Only Run Once

Side-note - it would be nice to know how much the reviews would have cost if we weren’t in free trial, so we have an idea of what cost cap to set next week.

1 Like

OK I just saw another thread with the same query - I missed it when I searched before, apologies for duplicating.

As the admin for my team, I absolutely assumed I was setting team-wide things here as I have both github admin and Cursor admin permissions. We all want the same behaviour from BugBot and I never assumed everyone in my team would need to set up the GH connection, especially as the reviews started occurring for all team members as soon I had set it up.

2 Likes

Thanks @sarah-gelt for reporting and for checking other threads, appreciate it. Saw your comment there too.

The BugBot calls are Max (API/context based), and team can set a spending limit.

Here is a bit more with updated docu

1 Like

Thank you. The updated documents are appreciated too! I’ll let my team know that they should each set their personal preferences.

As team admin, I would love the opportunity to have master control over that for the repo so that all members must have the same experience. You could also give admins the choice to allow users to personalise it themselves, so each team can allow or disallow team member customisation as suits their workflow.

1 Like

I asked my team members to set their own Personal Preferences to Only Run Once, but the first one who tried sees nothing on the Integrations page. Is that right?

Right, so the docu says:

After installing, team admins will see a list of available installations and their enabled repositories. Team admins can enable or disable BugBot per repository and setup allow/denylists for reviewers. Once enabled, BugBot will run for anyone contributing to the repository, whether or not they’re on your team.

Individual team members can customize how BugBot works for them: Run once, …

As team admin you already enabled all the required repo’s?

Yes, the repo is enabled and that same team member has an open PR at the moment which has already been reviewed by BugBot

@jkaplan could you please have a look what we are missing here with the BugBot integration?

1 Like

Hi! “Only run once” is in the personal settings, so that only applies to the person who checked that. Every team member can go in and modify their own personal settings in this regard.

Right, but in screenshot above their team member has nothing listed.

1 Like

Yep :confounded_face: I had another team member try and he also confirmed he gets a blank page, so it seems like I’m the only one who has any settings available in there.

Did your team member click Connect GitHub in the settings page? We can only store personal settings if someone is authenticated with GitHub

Just took a look at the screenshot and they don’t see anything, interesting. Will look into it

Indeed this was a bug, thank you for pointing it out! Should be fixed now (or in a few min as website redeploys), you can ask your teammate to go back into settings and they should see the Connect Github button. Please let me know if they still don’t!

1 Like

Amazing, thank you! It’s past close of business here in the UK now so I might not know until Monday but I will confirm then either way.

2 Likes

My team can now all see their settings and have updated them accordingly. So far so good with review behaviour :+1: Thanks again!

3 Likes