grafana/terraform-provider-grafana - Open Source PR Review Scorecard

Terraform Grafana provider

C-Rank Grade: A (Welcoming) - 60/100

External PR Merge Rate: 72%

Response Time: 9d

First Timer Success: 75%

Frequently Asked Questions

Is grafana/terraform-provider-grafana welcoming to first-time open-source contributors?

grafana/terraform-provider-grafana has a recorded first-timer success rate of 75.0%. Repositories ranked A 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 grafana/terraform-provider-grafana respond to incoming external pull requests in approximately 207.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 59.8 C-Rank™ score (A 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 59.8 places grafana/terraform-provider-grafana in the A tier.

What is the external contributor pull request merge rate for grafana/terraform-provider-grafana?

The external contributor pull request merge rate for grafana/terraform-provider-grafana is 71.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in grafana/terraform-provider-grafana?

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

grafana
grafana/terraform-provider-grafanaA•Welcoming511
GitHub
Back to Explorer
grafana

grafana/terraform-provider-grafana

511
Active (30d)A•Welcoming(60/100)Go

Terraform Grafana provider

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
5.0/10
Patience Score
6.0/10
Nitpick Rate
65%

Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in grafana/terraform-provider-grafana.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
8 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
71.7%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
43 core
Highly collaborative maintainer core
Diagnostic Health HUD
71.7%
Merge Gauge
75.0%
1st-Timer
Community Vibe51/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

Feature Request Description Today, the Grafana Terraform provider does not expose a way to configure signed SAML authentication requests for Grafana SSO. This makes it impossible for users who require signed AuthnRequests to fully manage their SAML configuration via Terraform. While SAML request signing is supported in Grafana, the corresponding option is not currently available in the Terraform provider, which can lead to configuration drift or force users to manage part of their SSO setup outside of Infrastructure as Code. Problem / Motivation Many IdPs (for example Okta, Azure AD, and Ping) require or strongly recommend signed SAML AuthnRequests. Without Terraform support for this setting: Users cannot fully manage SSO via Infrastructure as Code Terraform runs may overwrite or revert manually configured SSO settings Teams with security or compliance requirements are blocked from adopting Terraform for SSO Proposed Solution Extend the grafana_sso_settings resource to support conf

📅 Opened Jan 20, 2026💬 2 comments
Quality: 20/100Contribute
Looking for more Go beginner tasks?Explore Go 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 grafana/terraform-provider-grafana

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

Frequently Asked Questions - Contributing to grafana/terraform-provider-grafana

01

Is grafana/terraform-provider-grafana welcoming to first-time open-source contributors?

grafana/terraform-provider-grafana has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming 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 ~8 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 59.8 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 59.8 places grafana/terraform-provider-grafana in the Welcoming tier.

04

What is the external contributor pull request merge rate for grafana/terraform-provider-grafana?

The external pull request merge rate is 71.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 grafana/terraform-provider-grafana?

Yes, grafana/terraform-provider-grafana 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 grafana/terraform-provider-grafana 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.