fix(roast): 修正年度贡献数的错误归因 - #210
Open
ZJPex wants to merge 1 commit into
Open
Conversation
|
@ZJPex is attempting to deploy a commit to the hikariming's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
关联 Issue
关联 #209(不自动关闭)。
问题
last_year_contributions来自 GitHub 过去一年贡献日历的聚合计数,但锐评模型可能把它误写成 PR 数,并进一步据此推断贡献类型或仓库归属。例如 Issue #209 中的 payload 同时包含:
last_year_contributions = 694total_pr_count = 8merged_pr_count = 5原始 PR 统计是独立且正确的,错误发生在锐评生成阶段对字段语义的解释。
修复
context_notes.last_year_contributions_scope解释年度贡献总数;验证
pnpm test -- src/lib/__tests__/prompt.test.ts:28/28 通过pnpm typecheck:通过pnpm lint:通过(仅有未修改文件中的既有 warning)pnpm test:612/612 通过go test ./...:通过pnpm smoke:deployment:selftest:通过pnpm smoke:backend:async:selftest:通过pnpm smoke:backend:resilience:selftest:通过pnpm build:通过影响范围
该修改只约束新生成锐评对字段的解释,不改变贡献数、PR 数或评分结果。已经生成并缓存的旧锐评可能需要重新生成或等待缓存失效。