Review economics
buuing/lucky-canvas
Read from the 13 most recently merged pull requests ·
Not enough merged pull requests on both sides yet to compare how they land in review.
—
Attributed
0
Attributed PRs
13
Other PRs
13
Read
The rest — the latest 5
#360 fix: 修复老虎机 prizes 更新数据长度大于初始化时数据长度导致的展示问题
1 reviews · 7.5d to merge
#366 fix: close #284
1 reviews · 19h to merge
#353 fix: 修复 Taro-React 九宫格在 ScrollView 中，抽奖按钮点击无效和事件穿透问题
1 reviews · 0h to merge
#310 hotfix(react): 修改因为react18带来的使用上的问题：https://github.com/buuing/lucky-c…
1 reviews · 11h to merge
#194 fix: export config type
1 reviews · 28h to merge
How this was measured
No commit in this window carries agent attribution, so there is no AI-authored share to read here — which is not evidence there is none; tools that only complete code inline leave no commit trail, so the unattributed side includes AI-assisted work.
“Attributed” means a commit carried an agent’s signature — a co-author trailer, an agent commit identity, or an agent bot account. Tools that only complete code inline leave no such mark, so the other column is “rest”, not “human-written”. Full method and its limits
The badge reads this repo’s current report, so it follows the number.
Tell me when this moves
We re-read buuing/lucky-canvas weekly and email only when the number changes materially.
Read your own repos
This one is public. For a private repo, run the same read locally through your own GitHub credentials — nothing is installed and nothing is sent to us.
npx @ambera/review-taxWant this continuously on buuing/lucky-canvas — each pull request paired to the task it came from, and the work graded from its review loop rather than its diff size? Claim this repo in Forge
Browse every repo people have read · Read a different repository