/update: the bot is refused on contributors' forks (worked on the owner's fork), and it doesn't log why
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the /update workflow code and run 39116506769 to find where the update-branch API response is handled; add failure status and message logging without secrets. Reproduce the request on a contributor fork and compare it with the successful maintainer call. Update CONTRIBUTING.md and docs/AGENT_WORKFLOW.md to describe the confirmed behavior; done when the cause is confirmed and the docs match.
由索引模型根据 Issue 内容生成。
描述
Follow-up to #472 (#464).
During its pre-merge test, /update could update a branch in itsskofficial/Sentient, the repo owner's own fork. On the first real use, on #407 from syedmustafan/Sentient with "Allow edits by maintainers" on, PUT /pulls/{n}/update-branch with the workflow token was refused. The fallback worked as designed: the button hint plus the needs update label. A maintainer then ran the same API call with their own credentials and it succeeded.
So the built-in GITHUB_TOKEN probably can't push to forks owned by other people. It only worked on the admin's own fork. The run log (run 39116506769) also doesn't show the status or message GitHub returned, so this can't be confirmed from the log.
To do:
- Log the update-branch response status and message (no secrets) whenever it fails.
- Confirm the cause on a contributor fork, and update CONTRIBUTING.md and docs/AGENT_WORKFLOW.md to match. The likely result is that
/updatemerges main on same-repo branches only, and on forks it offers the button and labels the PR for a maintainer. That is fine with our policy, because maintainers handle labelled PRs. - Only if the owner wants it: a GitHub App with contents:write could update fork branches. That needs a setup decision, so don't add new secrets without asking.
- 主要语言
- Python
- 星标
- 702
- 派生
- 113
- 平均合并
- 5 小时 8 分钟
- 30 天内合并 PR
- 171
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
existence-master/Sentient 的其他 Issue
-
area: channels enhancement good first issue priority: P2 size: S
难度 2/5 1-3 小时 新手友好度 78/100
existence-master/Sentient#457 ·
维护者通常 1 天内回复
-
area: desktop bug good first issue priority: P2 size: S
难度 2/5 1-3 小时 新手友好度 82/100
existence-master/Sentient#454 ·
维护者通常 1 天内回复
-
area: desktop bug priority: P2 size: S
难度 2/5 1-3 小时 新手友好度 82/100
existence-master/Sentient#440 ·
维护者通常 1 天内回复
-
area: desktop bug
难度 2/5 1-3 小时 新手友好度 78/100
existence-master/Sentient#426 ·
维护者通常 1 天内回复
-
area: memory bug flaky
难度 2/5 1-3 小时 新手友好度 76/100
existence-master/Sentient#422 ·
维护者通常 1 天内回复
查看 existence-master/Sentient 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 79/100
SACGF/variantgrid#2341 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
comp/cli P3 type/security
难度 2/5 1-3 小时 新手友好度 68/100
NousResearch/hermes-agent#141420 · 1 条评论 ·
维护者通常 1 天内回复
-
CKV_GCP_18 (GKEPublicControlPlane) passes when master_authorized_networks_config is absent, control plane is internet-reachable可能已有人在做 @Varshith-Kali 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
bridgecrewio/checkov#7753 ·
维护者通常 1 天内回复