Review economics
gzu-liyujiang/AndroidPicker
Read from the 21 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
21
Other PRs
21
Read
The rest — the latest 5
#365 1.毫秒设置成1000,实际上获取出来的时间是下个月的1号0点，改为999，防止出现其他月份；2. 滑动日历时，添加对月份变化的监听
0 reviews · 48h to merge
#346 新增功能 滚动到尽头就不可以再拖动
1 reviews · 34h to merge
#329 删除多余的条件判断，前面的代码已经判断过了
1 reviews · 20h to merge
#240 [message]:欧洲要求最低complieSdkTarget 29,需要迁移androidx，在1.5.6基础上迁移到androix，…
0 reviews · 5.2d to merge
#231 Refactor 2.0
0 reviews · 0h 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 gzu-liyujiang/AndroidPicker 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 gzu-liyujiang/AndroidPicker — 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