[sentry-junior]

When Junior opens a PR on top of another PR's branch, the PRs form a plain base-branch chain. GitHub does not know they are a stack, so it cannot rebase them or merge them as one group. #2597 and #2598 taught the merge and conflict steps to use gh stack when a stack exists, but Junior never created one.

github_createPullRequest now links the new PR into a native GitHub stack (docs).

• Skip when the base is the repo's default branch or the head repo is a fork. Normal PRs get no extra calls.
• Walk down the base branches through open PRs (up to 10 levels) to find the chain.
• If the parent PR is the top of a stack, add the new PR to that stack (POST /stacks/{n}/add). If the parent is in the middle of a stack, skip. Otherwise create a stack from the bottom PR to the top (POST /stacks).
• The tool result returns stack: { number, pullRequests } when the link succeeds.

Stacking is optional, like requester assignment. A rejected call logs github.pull_request.stack_after_create.rejected, and an exception logs github.pull_request.stack_after_create.failed. PR creation never fails because of stacking.

Known gaps:

• A replayed create call (the PR already exists) does not stack.
• Junior watches only the PRs it opens. If a person owns the bottom PR, Junior does not get its merge event.

via @BYK.

--

View Session in Sentry

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
junior-docs	Ready	Preview	Nov 3, 2026 9:33pm UTC

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ba7f62a. Configure here.}