Instant hot reload & fast incremental compilation plugin for Android Studio. See changes in 3 seconds without Gradle overhead.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
tencentmusic/jugg has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tencentmusic/jugg respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 7.5 places tencentmusic/jugg in the D tier.
The external contributor pull request merge rate for tencentmusic/jugg is 0.0%, based on public PR activity from non-core contributors.
tencentmusic/jugg currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in tencentmusic/jugg. Reviews community pull requests with focus on project quality.
Discussions in tencentmusic/jugg focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/tencentmusic/jugg?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~168 hours (81% approval). Large PRs (>500 lines) take ~1237 hours (29% approval). Keep your diff compact for rapid review.
问题类型 其他 问题描述与复现 问题表现 cpu占用过高，编辑代码是卡顿 诊断材料类型（按优先级任选一种） Jugg Report ID（最推荐） 诊断材料 编译问题 提交确认 我已搜索现有 Issue，未发现相同 bug 描述。
使用场景与问题 在 Android 项目中使用 Room 时，当 Entity、Dao、数据库版本或相关接口发生变化，Jugg 当前会直接执行 fallback，退回 Gradle 编译。 Room 的接口变更并不一定都会影响所有模块或所有生成代码。当前一旦触发 fallback，增量编译的速度优势会明显降低，开发反馈时间变长。 期望结果 希望 Jugg 能识别 Room 相关接口变更的影响范围，并在安全的情况下提供兼容处理： 对可以增量处理的 Room 变更，尽量继续使用 Jugg 的增量编译能力； 对确实无法安全增量处理的变更，再执行 fallback； 如果暂时无法兼容，希望在日志中明确说明触发 fallback 的具体原因，以及对应的变更类型； 不影响现有编译结果的正确性，无法确认安全时应优先保证构建正确。 补充信息 这里的诉求不是取消 fallback，而是希望针对 Room 生成代码的特点增加更细粒度的变更识别和
问题类型 运行时不生效 问题描述与复现 问题表现 通过git stash pop了之前的一些代码，包含了新增的Activity，Activity注册使用的ARouter，编译之后点击对应的跳转报错找不到对应的路由，我猜应该是没有把新增的路由构建编译出来 诊断材料类型（按优先级任选一种） 手工诊断信息（仅当前三项均不可用） 诊断材料 提交确认 我已搜索现有 Issue，未发现相同 bug 描述。
功能建议 使用场景与问题 使用了下AS的效果特别好,已经推荐给团队使用了 期望结果 期望能把鸿蒙/iOS的版本也做出来 整个团队提效 补充信息 提交确认 我已搜索现有 Issue，未发现相同功能请求。
问题类型 编译失败 问题描述与复现 问题表现 使用外部 agent 修改文件，偶发的未识别到文件修改，导致出现 java.lang.NoSuchMethodError， 手动修改后恢复 复现步骤 诊断材料类型（按优先级任选一种） Jugg Report ID（最推荐） 诊断材料 E AndroidRuntime: java.lang.NoSuchMethodError 提交确认 我已搜索现有 Issue，未发现相同 bug 描述。
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to tencentmusic/jugg, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of tencentmusic/jugg acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
tencentmusic/jugg has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 7.5 places tencentmusic/jugg in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tencentmusic/jugg currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tencentmusic/jugg are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.