Review economics
elunez/eladmin
Read from the 83 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
83
Other PRs
83
Read
The rest — the latest 5
#889 fix:SqlUtils获取连接的私有方法无需关闭连接，在其他使用的地方已有关闭连接的写法，否则executeFile执行时获取连接后连接被关闭则无法真正执行sql。
0 reviews · 52.9d to merge
#887 fix:修复自定义@Async线程池的线程命名总是为el-async-1的问题
0 reviews · 30.0d to merge
#880 fix and close https://github.com/elunez/eladmin/issues/874
0 reviews · 54.8d to merge
#810 fix(LimitAspect): 修复lua脚本执行结束后，类型转换失败的bug
0 reviews · 418.7d to merge
#809 fix(EmailServiceImpl): 解决由于jdk8之后默认禁用了部分tls协议，从而导致发送邮件失败的问题
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 elunez/eladmin 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 elunez/eladmin — 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