Author approval credit
作者审批积分
The approval policy needs author experience to contribute enough points for an established author and one ordinary reviewer to meet the two-point requirement.
English
Problem
The approval policy needs author experience to contribute enough points for an established author and one ordinary reviewer to meet the two-point requirement.
Decision
The approval policy awards 0.011 points per merged PR in this repository, capped at 1.1 points after 100 PRs. History lookup stops at 100 matching PRs. Author credit alone remains insufficient, and blocking reviews still prevent approval.
Alternatives considered
Keep the 0.6-point cap at 150 PRs. That cap cannot combine with an ordinary one-point review to meet the requirement without an ownership boost.
Consequences
One ordinary approval with no ownership boost meets the requirement at 91 merged PRs; 90 yields only 1.99 points. The lower counting cap limits required history traversal for prolific authors. Merged PR count measures contribution history rather than review quality.
Verification
Policy tests cover credit below, at, and above the cap; the 90/91-PR approval threshold; author-only rejection; pagination; and below-threshold scores whose display rounds to two.
中文
Problem
审批策略需要让作者经验贡献足够的积分，使有经验的作者与一位普通审阅者能够共同满足两分要求。
Decision
审批策略为作者在本仓库中每个已合并 PR 计入 0.011 分，达到 100 个 PR 时以 1.1 分封顶。历史查询在找到 100 个匹配 PR 后停止。仅靠作者积分仍不足以通过审批，阻塞性审阅仍会阻止通过。
Alternatives considered
保留 150 个 PR 时封顶 0.6 分的规则。 在没有代码所有权加分的情况下，该上限与普通审阅的一分相加仍无法满足要求。
Consequences
没有代码所有权加分时，一次普通批准与 91 个已合并 PR 的作者积分相加即可满足要求；90 个则只有 1.99 分。较低的计数上限减少了高贡献作者所需的历史遍历。已合并 PR 数量衡量贡献历史，而非审阅质量。
Verification
策略测试覆盖积分低于、达到及超过上限的情况、90/91 个 PR 的审批阈值、仅靠作者积分不能通过、分页，以及显示值舍入为两分但实际低于阈值的情况。