create_pull_request / update_pull_request return an error after the PR was created or edited (reviewer step fails)

未关闭
#3,756 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
57/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
github, go

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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 gets A 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.)

  1. Call it with the authenticated user (the PR author) as reviewer:
    {"name":"create_pull_request","arguments":{"owner":"OWNER","repo":"REPO","title":"t","head":"feature","base":"scratch-base","body":"b","reviewers":["<authenticated user's login>"]}}
    
    Result: isError with failed to request reviewers: Review cannot be requested from pull request author.. GET /pulls?head=OWNER:feature shows the PR open.
  2. Repeat the same call. Result: failed to create pull request: Validation Failed … A pull request already exists for OWNER:feature.
  3. Step 1 with "reviewers":["octocat"] (not a collaborator) behaves the same way.
  4. Step 1 with "reviewers":["no-such-user-zz9"] returns success {"id":"…","url":".../pull/N"}, and requested_reviewers is empty.
  5. Call:
    {"name":"update_pull_request","arguments":{"owner":"OWNER","repo":"REPO","pullNumber":123,"title":"changed","reviewers":["<author login>"]}}
    
    Result: isError (failed to request reviewers: …), but GET /pulls/N shows title: "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.

主要语言
Go
星标
34.2k
派生
5.3k
平均合并
5 天 18 小时
30 天内合并 PR
13

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/github-mcp-server 的其他 Issue

查看 github/github-mcp-server 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。