The Official QuickBars for Home Assistant Repository
C-Rank Grade: D (Risky) - 29/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
Trooped/QuickBars 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 Trooped/QuickBars respond to incoming external pull requests in approximately 0.2 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 29.3 places Trooped/QuickBars in the D tier.
The external contributor pull request merge rate for Trooped/QuickBars is 0.0%, based on public PR activity from non-core contributors.
Trooped/QuickBars currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in Trooped/QuickBars. Reviews community pull requests with focus on project quality.
Discussions in Trooped/QuickBars 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/Trooped/QuickBars?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~1 hours (29% approval). Keep your diff compact for rapid review.
⚠️ Rules of Engagement Please read before submitting: Language: All issues must be submitted in English. Completeness: You must fill out all sections of this template. Respect: This project is maintained by a student/developer in their spare time; help me help you by being clear. Automatic Closure: Issues that are not in English or are incomplete will be closed immediately. Describe the bug When attempting to launch certain third-party apps (frequently telecom, provider, or sideloaded mobile apps) via QuickBars, the app fails to open and displays a "Can't open [package_name] (no launchable activity)" toast. This happens because these specific apps omit the standard Android TV CATEGORY_LEANBACK_LAUNCHER intent from their manifest. As a result, QuickBars' standard intent resolution cannot find the "front door" to launch them. To Reproduce Steps to reproduce the behavior: Configure a trigger key in QuickBars to open an app known to lack a leanback intent (e.g., a provider app like
Regarding the volume control issue on some TV models when turning the Accessibility on. There is another app called tvQuick Actions pro (Quick Start Guide - tvQuickActions Docs) which addresses the volume issue by temporarily disabling accessibility services for 10 seconds when the Volume (+) or (-) is pressed. Do you think you could implement a similar workaround for QuickBars? Probably would help make your app work for most TV manufacturers.
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 Trooped/QuickBars, 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 Trooped/QuickBars acknowledge new external contributions in approximately <1 hour. 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.
Trooped/QuickBars 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 ~<1 hour. 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 29.3 places Trooped/QuickBars 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, Trooped/QuickBars 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 Trooped/QuickBars 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.