Noticed a false positive early from bugbot, resolved the comment with false positive comment, but can’t find a way to stop/cancel the autofix run, meaning instead of a 1 min run stopped early, it goes the whole run wasting 9 mins worth of token usage unnecessarily.
I’d like to bump up the priority of this feature request. It’s pretty irritating having to wait for Bugbot to “fix” something I don’t agree should be fixed in the first place. At some point it even timed out after 30 minutes (probably due to GitHub’s timeout limit).
Additionally, it would be great be able to specify which branches or PRs to exclude Bugbot runs from. That would actually make me have to manually cancel fewer runs.
Hey, thanks for the feedback. The request is clear. Having to wait while Bugbot fixes something you already flagged as a false positive is really annoying, and it also wastes money.
Right now there isn’t a separate Cancel button for a running autofix run. There’s only an auto-timeout and cancel on error. So yes, that’s a real gap for now, and we’re tracking it as a feature request. I can’t share an ETA.
On the second part about excluding specific branches or PRs from Bugbot, there’s already a thread on that exact topic. It makes sense to add your vote and details there so the signal doesn’t get diluted: Bugbot - run only on specific Github branches
If anyone else has specific mid-run cancel scenarios, post them here. It helps us prioritize.