Kubernetes operator for managing Valkey on Kubernetes (WIP).
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 75%
Response Time: 2d
First Timer Success: 93%
valkey-io/valkey-operator has a recorded first-timer success rate of 93.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in valkey-io/valkey-operator respond to incoming external pull requests in approximately 46.7 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 62.2 places valkey-io/valkey-operator in the A tier.
The external contributor pull request merge rate for valkey-io/valkey-operator is 75.2%, based on public PR activity from non-core contributors.
valkey-io/valkey-operator currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (70% positive review sentiment). Active code reviews with constructive guidance for new contributors in valkey-io/valkey-operator.
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/valkey-io/valkey-operator?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~30 hours (94% approval). Large PRs (>500 lines) take ~224 hours (34% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
The verification layer for coding agents
Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.
Dynamic, resilient AI orchestration. Coordinate data, models, and compute as you build AI workflows.
Follow-up from #319. ACLApplied compares the user set and each user's password hashes, so adding or removing a user or a password moves it through PendingPropagation back to True. A change to a user's enabled flag or permissions still takes effect on the server (the reload is unconditional), but the condition does not report a transient PendingPropagation for those fields, so it is not a signal to wait on for them. This is documented under ACLApplied in docs/status-conditions.md. Why permissions are not compared directly: ACL GETUSER returns Valkey's normalized rendering of the rules, while the operator only holds the aclfile text, so a field-by-field comparison would mean reimplementing Valkey's ACL parser. Proposed fix Append a revision sentinel to the aclfile: a disabled user (_operator_acl_sentinel off) whose only password hash is a hash of the whole managed ACL. It flows through the existing user and hash comparison, so ACLApplied reads True only once the running server has loaded
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 valkey-io/valkey-operator, 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 valkey-io/valkey-operator acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.2% were successfully merged into the primary branch.
valkey-io/valkey-operator has a recorded first-timer success rate of 93.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 62.2 places valkey-io/valkey-operator in the Welcoming tier.
The external pull request merge rate is 75.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, valkey-io/valkey-operator 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 valkey-io/valkey-operator 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.