We set up BugBot for our organization today. I submitted my first PR since, and still waiting to see BugBot action on it.
Hey, ideally it should start working immediately, but if it doesn’t, you can try running it manually. BugBot is still in beta, so issues might occur. Also, feel free to share your impressions or any problems you encounter.
@troehrkasse By default BugBot would comment that no issues were found, which can be adjusted if you prefer not have those comments.
@deanrie @T1000 thanks for the responses. I’ve created a second PR and so far don’t see any action on either of them from Bugbot. On one, I tried commenting bugbot run on one of them, and that does not appear to trigger anything either. After some time I tried commenting bugbot run verbose=true and again, nothing shows up.
Here are some screenshots of the setup. It seems to be done correctly. Is there any specific area we should check?
As you can see we have it enabled for just one repository, which is the one I’m using for my tests, here’s my latest example PR:
cc @danperks
We checked these settings and it looks the same as on your screenshot, all three toggles are disabled.
@deanrie @danperks On a whim I logged into Cursor and went to my integrations tab and it shows nothing is set up:
Does each member of our team need to set up this integration? Only my boss set this up, he is the admin of our team both on Cursor and on Github. He is the one who set this integration up and we were under the impression that would allow it to work for our whole team.
If a team admin enables BugBot on a repo, it should run for everyone contributing to that repo. You can trigger a run manually by commenting “bugbot run” as a GitHub comment.
From your last screenshot, if you click “Connect GitHub” you will see all the repos that you have access to that BugBot is installed on. That should be your source of truth for if BugBot is enabled on that repo.
I did click Connect to Github, and now I see the same settings as on my boss’s settings page.
Bugbot is enabled with default settings, for one repository, and there is no PR filter applied. At this point myself and other team members have created many new PRs in this repository but Bugbot is not running on any of them. We have tried commenting bugbot run to trigger it manually but this doesn’t work either.
Very interesting! Will look into this, could you please do a “bugbot run verbose=true”? It should comment a requestId that we can look into. If it doesn’t do that, let me know
