ClickHouse/ClickBench - Open Source PR Review Scorecard

ClickBench: a Benchmark For Analytical Databases

C-Rank Grade: S (Elite) - 70/100

External PR Merge Rate: 74%

Response Time: 1d

First Timer Success: 76%

Frequently Asked Questions

Is ClickHouse/ClickBench welcoming to first-time open-source contributors?

ClickHouse/ClickBench has a recorded first-timer success rate of 76.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in ClickHouse/ClickBench respond to incoming external pull requests in approximately 27.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 70.4 C-Rank™ score (S Tier) represent?

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 70.4 places ClickHouse/ClickBench in the S tier.

What is the external contributor pull request merge rate for ClickHouse/ClickBench?

The external contributor pull request merge rate for ClickHouse/ClickBench is 73.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in ClickHouse/ClickBench?

ClickHouse/ClickBench currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

ClickHouse
ClickHouse/ClickBenchS•Elite1.1k
GitHub
Back to Explorer
ClickHouse

ClickHouse/ClickBench

1,128
Active (30d)S•Elite(70/100)Shell

ClickBench: a Benchmark For Analytical Databases

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.8/10
Patience Score
8.8/10
Nitpick Rate
25%

Highly welcoming maintainers in ClickHouse/ClickBench. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
1 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
73.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
76.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
29 core
Highly collaborative maintainer core
Diagnostic Health HUD
73.7%
Merge Gauge
76.0%
1st-Timer
Community Vibe62/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for ClickHouse/ClickBench
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/ClickHouse/ClickBench)](https://getmerged.abhishekco.de/ClickHouse/ClickBench?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Hi! The current CHYT benchmark results in the repository are from 2024. CHYT has changed significantly since then, so it would be great to rerun the benchmarks and update the results. Thanks!

📅 Opened Aug 18, 2026💬 0 comments
Quality: 35/100Contribute
Looking for more Shell beginner tasks?Explore Shell GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for ClickHouse/ClickBench

When evaluating whether to contribute to ClickHouse/ClickBench, 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 ClickHouse/ClickBench acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.7% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to ClickHouse/ClickBench

01

Is ClickHouse/ClickBench welcoming to first-time open-source contributors?

ClickHouse/ClickBench has a recorded first-timer success rate of 76.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 70.4 C-Rank™ score represent?

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 70.4 places ClickHouse/ClickBench in the Elite tier.

04

What is the external contributor pull request merge rate for ClickHouse/ClickBench?

The external pull request merge rate is 73.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in ClickHouse/ClickBench?

Yes, ClickHouse/ClickBench currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for ClickHouse/ClickBench 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.