Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 70%
Response Time: 20h
First Timer Success: 71%
woodpecker-ci/woodpecker has a recorded first-timer success rate of 70.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in woodpecker-ci/woodpecker respond to incoming external pull requests in approximately 20.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 66.6 places woodpecker-ci/woodpecker in the A tier.
The external contributor pull request merge rate for woodpecker-ci/woodpecker is 69.7%, based on public PR activity from non-core contributors.
woodpecker-ci/woodpecker currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (71% positive review sentiment). Active code reviews with constructive guidance for new contributors in woodpecker-ci/woodpecker.
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/woodpecker-ci/woodpecker?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (87% approval). Large PRs (>500 lines) take ~96 hours (31% approval). Keep your diff compact for rapid review.
Clear and concise description of the problem path conditions are only evaluated for push and pull_request events (constraint.go#L184-186). On a tag event the path filter is silently ignored and the step always runs, even when written in the same when entry: when: - event: tag path: images/foo/** # no-op on tag; step runs regardless This makes it impossible to gate work on a tagged release by what changed. The concrete use case is a release pipeline that rebuilds only the images whose build context changed since the previous tag. Suggested solution Evaluate path for event: tag as it is for push/PR, diffing previousTag..tag. when: - event: tag path: images/foo/** # runs only if images/foo changed since the previous release Defining "previous tag" is a design decision. The natural default is the nearest tag in the tagged commit's ancestry (git describe --tags --abbrev=0 <tag>^), i.e. graph-nearest; this equals the previous release on linear tag history. Graph-distance, cre
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 woodpecker-ci/woodpecker, 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 woodpecker-ci/woodpecker acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.7% were successfully merged into the primary branch.
woodpecker-ci/woodpecker has a recorded first-timer success rate of 70.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 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 66.6 places woodpecker-ci/woodpecker in the Welcoming tier.
The external pull request merge rate is 69.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, woodpecker-ci/woodpecker currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for woodpecker-ci/woodpecker 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.