My team recently started using the new GitHub stacks feature. Right now it’s looking like BugBot is reviewing each PR in the stacks independently, but is it actually looking at the context of the stack as a whole? If not, could we give it “hints” until then, e.g. put something in the PR description to say a PR is part of a stack and where to find the rest of it?
You’re right that BugBot doesn’t have stack awareness yet. It reviews each PR against its own base branch, so it only sees that PR’s own changes and doesn’t pull in the diffs or comments from the other PRs in the stack.
One reassuring bit: because each PR is built on the ones below it, the code from the earlier PRs is still present in the checkout BugBot reviews, so it can read that context when it needs to. It just doesn’t know the PR is part of a stack.
Hints do help in the meantime:
- PR description. Whatever’s in the PR title/description is passed to BugBot, so a note like “PR 2 of 3 in a stack; parent is #123, child is #125” will be seen and used.
.cursor/BUGBOT.md. For something permanent, add a repo rule describing your stacking convention. It’s applied automatically on every review.
One caveat: even with hints, BugBot won’t go fetch the other PRs’ contents, so the hint gives it context rather than the actual sibling diffs. It’s a fair ask though, so I’ll capture stack-aware reviews as interest for the team.
Let me know if that helps!
I’ll give it a try - thanks for the tips!