Prow is a Kubernetes based CI/CD system developed to serve the Kubernetes community. This repository contains Prow source code and Hugo sources for Prow documentation site.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 49%
Response Time: 3h
First Timer Success: 100%
kubernetes-sigs/prow has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kubernetes-sigs/prow respond to incoming external pull requests in approximately 3.1 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 64.8 places kubernetes-sigs/prow in the A tier.
The external contributor pull request merge rate for kubernetes-sigs/prow is 48.6%, based on public PR activity from non-core contributors.
kubernetes-sigs/prow does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Balanced & professional review environment in kubernetes-sigs/prow. Maintains strict focus on technical quality and test standards.
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/kubernetes-sigs/prow?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 Monday - Wednesday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (61% approval). Large PRs (>500 lines) take ~15 hours (22% approval). Keep your diff compact for rapid review.
It is already possible to trigger all tests with /test all, and to rerun any failed tests with /retest. I would want to expand on this by making it possible to trigger all required jobs that may not have run yet. The background is that we commonly have a couple of required, but NOT automatically triggered tests in the metal3-io project. This helps us save resources. Contributors and/or reviewers trigger these tests manually when ready. We don't want to /test all though, that would trigger a bunch of tests that are rarely necessary. We just want those required tests to run. What we currently do is simply to copy the test name from the pending checks and trigger them with /test <name-of-test-1> <name-of-test-2>, as seen below. This works but it gets annoying after a while, especially when you have to do it across multiple dependabot PRs throughout all the repositories. So to simplify, I would like to be able to do /test-required and be done with it.
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 kubernetes-sigs/prow, 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 kubernetes-sigs/prow acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.6% were successfully merged into the primary branch.
kubernetes-sigs/prow has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 hours. 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 64.8 places kubernetes-sigs/prow in the Welcoming tier.
The external pull request merge rate is 48.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kubernetes-sigs/prow does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for kubernetes-sigs/prow 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.