create_pull_request / update_pull_request return an error after the PR was created or edited (reviewer step fails)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, go
- Domain
- api, backend-api-design
Research direction
Start with pkg/github/pullrequests.go at PullRequests.Create and PullRequests.Edit, then follow their reviewer and draft-state error paths. Check how the tool formats successful results and errors so a partial failure can still report the PR number and URL alongside the failed follow-up. Done means create and update results preserve the successful PR change details when reviewer or draft steps fail, with coverage for those cases.
Written by the indexing model from the issue text.
Description
Describe the bug
Both tools do several REST and GraphQL calls in sequence. If the reviewer request fails after the main call has succeeded, the tool returns isError with only the reviewer error:
create_pull_request: the PR has been created, but the error text has no PR number or URL. A caller that retries getsA pull request already exists for OWNER:head, and still has no number.update_pull_request: the title (and any other edited fields) has already been applied, but the result is an error, so a caller will assume nothing changed.
Conditions (tested): the reviewer request fails with GitHub 422 when the reviewer is the PR author ("Review cannot be requested from pull request author.") or is not a collaborator ("Reviews may only be requested from collaborators…"). A login that doesn't exist does not fail: GitHub accepts the request, the tool reports success, and the PR ends up with no requested reviewer.
Code (main 99d6d650, unchanged since v2.1.0): pkg/github/pullrequests.go:855 (PullRequests.Create), then :874-899 (RequestReviewers; on failure it returns NewGitHubAPIErrorResponse(ctx, "failed to request reviewers", …) (:882; the status variant at :899 is only reached for a non-2xx response without a Go error) and drops pr). For updates: :1090 (PullRequests.Edit), :1109-1173 (draft-state GraphQL mutation), then :1176-1209 (error return at :1190) (RequestReviewers, same error path). By code reading, the draft mutation step can partially apply the same way. Not tested.
Related: #3424 (open; clients cannot tell 'refused' from 'may have happened' for write errors).
Affected version
v2.1.0 (image sha256:f6056fc1…0f8a, commit 4bcdcdf8) and main nightly (image sha256:48bc16d0…338f, revision 99d6d650).
Steps to reproduce the behavior
(123 stands for the issue/PR number.)
- Call it with the authenticated user (the PR author) as reviewer:
Result:{"name":"create_pull_request","arguments":{"owner":"OWNER","repo":"REPO","title":"t","head":"feature","base":"scratch-base","body":"b","reviewers":["<authenticated user's login>"]}}isErrorwithfailed to request reviewers: Review cannot be requested from pull request author..GET /pulls?head=OWNER:featureshows the PR open. - Repeat the same call. Result:
failed to create pull request: Validation Failed … A pull request already exists for OWNER:feature. - Step 1 with
"reviewers":["octocat"](not a collaborator) behaves the same way. - Step 1 with
"reviewers":["no-such-user-zz9"]returns success{"id":"…","url":".../pull/N"}, andrequested_reviewersis empty. - Call:
Result:{"name":"update_pull_request","arguments":{"owner":"OWNER","repo":"REPO","pullNumber":123,"title":"changed","reviewers":["<author login>"]}}isError(failed to request reviewers: …), butGET /pulls/Nshowstitle: "changed". A non-collaborator reviewer behaves the same.
Expected vs actual behavior
Expected: when the PR was created or edited, the result says so and includes the number and URL, with the reviewer failure reported as a warning or partial failure ("PR N created; requesting reviewers failed: …").
Actual: a bare error, which reads as if nothing happened. On create, the PR number is lost, and a retry can't recover it.
Suggested fix: after a successful create or edit, don't return early on reviewer or draft errors. Return the normal result with the PR number and URL, plus a message listing which follow-up steps failed. Optionally, validate reviewers (author or collaborator) before creating.
Logs
create_pull_request reviewers=[author] -> ISERROR failed to request reviewers: Review cannot be requested from pull request author. (PR created)
retry -> ISERROR failed to create pull request: Validation Failed / PullRequest (custom): A pull request already exists for OWNER:feature.
create_pull_request reviewers=[octocat] -> ISERROR failed to request reviewers: Reviews may only be requested from collaborators. … (PR created)
create_pull_request reviewers=[no-such-user] -> OK {"id":"…","url":"…/pull/N"}; requested_reviewers []
update_pull_request title+reviewers=[author] -> ISERROR failed to request reviewers: …; title after = "changed"
Same results on v2.1.0 and main.
Found during an independent audit of v2.1.0 on a throwaway org and private test repo. Prepared with AI assistance (Claude Code); reproduced by two independent test runs before filing.
- Dominant language
- Go
- Stars
- 34.2k
- Forks
- 5.3k
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 13
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/github-mcp-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3760 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
github/github-mcp-server#3758 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
github/github-mcp-server#3729 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3722 ·
Maintainers usually reply within 2 days
-
Insiders Feedback: PR created UI doesn't link to the PRPossibly taken @genius-0963 claimed this 5 days ago. Openbug insiders user-experience
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/github-mcp-server#3658 ·
Maintainers usually reply within 2 days
All issues in github/github-mcp-server
Similar issues
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hexlet-basics/hexlet-basics#962 ·
Maintainers usually reply within 1 day
-
imapproxy closeForMaintenance grace timer calls clientConn.Close() before closeMaintenanceTransportPossibly taken @dejanstrbac claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
renovate-health
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Netcracker/qubership-network-latency-exporter#267 ·
Maintainers usually reply within 1 day
-
Network capture does not workPossibly taken @KSpaceer claimed this today. Openkind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aquasecurity/tracee#5395 ·