Bugbot is configured to run only once per pull/merge request. However, after Bugbot has already completed its review on an open PR, it got triggered again when dev merged develop into PR branch
Expected behavior:
Bugbot should perform a single review for the lifetime of the PR when configured as “once per PR”.
Subsequent updates to the same PR should not trigger another Bugbot review.
Steps to Reproduce
Configure Bugbot to run once per PR.
Create a new pull/merge request.
Wait for Bugbot to complete its initial review.
Update the same PR by adding new commits, rebasing, or merging the target branch into the source branch.
Push the updated branch and allow the PR to refresh.
Observe Bugbot behavior.
Hi Neha, Thanks for the detailed report — you’re right, and this is definitely unintended behavior.
What seems to be happening is that when “Once Per PR” is set as a personal setting, the “already reviewed” check is evaluated against the user who triggers the update. When a teammate merges your target branch (e.g., develop) into the PR, GitHub treats that teammate as the actor — and if they don’t also have “Once Per PR” set, Bugbot reviews again.
Workaround: Enable “Run Once Per PR” at the team/installation level (Bugbot dashboard → your installation’s settings). That applies to every update regardless of who pushes, so it won’t re-trigger on a teammate’s merge. As a team admin, you have access to this. Note that you’ll need to click first on the Github Org under Repositories: https://cursor.com/dashboard/bugbot#repositories This setting applies to all PRs raised in that org. You can select Run Once per PR and this should work across your team.
