nodejs / nodejs/node-core-utils
Force push does not invalidate existing approved reviews
未关闭
还没有人认领这个 Issue。
bug
- 主要语言
- JavaScript
- 星标
- 314
- 派生
- 137
- 平均合并
- 2 天 8 小时
- 30 天内合并 PR
- 24
描述
If the author force pushes to their branch after a reviewer approved it, I assumed that it would invalidate existing approved reviews, since the code that was reviewed is changed. But right now approved reviews count as valid ones, and might lead to unwanted code to be merged to main.
Example https://github.com/nodejs/node/pull/46904
➜ node git:(main) ✗ git node metadata 46904
✔ Done loading data for nodejs/node/pull/46904
----------------------------------- PR info ------------------------------------
Title url: use private properties for brand check (#46904)
Author Yagiz Nizipli <yagiz@nizipli.com> (@anonrig)
Branch anonrig:url-context -> nodejs:main
Labels semver-major, performance, whatwg-url, esm, author ready, worker, needs-ci
Commits 1
- url: use private properties for brand check
Committers 1
- Yagiz Nizipli <yagiz@nizipli.com>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/46904
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
--------------------------------------------------------------------------------
ℹ This PR was created on Wed, 01 Mar 2023 21:28:43 GMT
✔ Approvals: 3
✔ - Antoine du Hamel (@aduh95) (TSC): https://github.com/nodejs/node/pull/46904#pullrequestreview-1320667498
✔ - Ruben Bridgewater (@BridgeAR) (TSC): https://github.com/nodejs/node/pull/46904#pullrequestreview-1320668469
✔ - Benjamin Gruenbaum (@benjamingr): https://github.com/nodejs/node/pull/46904#pullrequestreview-1321281126
✖ This PR needs to wait 21 more hours to land
✖ GitHub CI is still running
ℹ Last Full PR CI on 2023-03-02T23:13:10Z: https://ci.nodejs.org/job/node-test-pull-request/50175/
✔ Build data downloaded
✖ Last Jenkins CI still running
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
该 issue 没有指出源文件、测试或入口点。首先在 node-core-utils 中定位 review 和 force-push 的处理逻辑,并复现 nodejs/node#46904 场景;完成的标准是:经过 review 的分支被 force-push 后,approval 不再计数,并且有覆盖该行为的测试。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- github, javascript
- 领域
- tooling
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100