lxc/terraform-provider-incus - Open Source PR Review Scorecard

Incus provider for Terraform/OpenTofu

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

External PR Merge Rate: 94%

Response Time: 9h

First Timer Success: 100%

Frequently Asked Questions

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

lxc/terraform-provider-incus 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.

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

Maintainers in lxc/terraform-provider-incus respond to incoming external pull requests in approximately 8.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 58.3 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 58.3 places lxc/terraform-provider-incus in the A tier.

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

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

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

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

lxc
lxc/terraform-provider-incusA•Welcoming215
GitHub
Back to Explorer
lxc

lxc/terraform-provider-incus

215
InactiveA•Welcoming(58/100)Low Sample (<20 PRs)Go

Incus provider for Terraform/OpenTofu

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.5/10
Patience Score
8.6/10
Nitpick Rate
30%

Highly welcoming maintainers in lxc/terraform-provider-incus. 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
8 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
94.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
94.4%
Merge Gauge
100.0%
1st-Timer
Community Vibe91/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Description I am trying to upload a GZIP file to my server, using the file block in incus_instance. Usually, terraform resources has an option to provide the content in base64 and decode it when writing the content of the file (e.g. local_file resource has a content_base64 attribute). Ideally it should be possible to have a similar option to be able to upload binary content. Steps to Reproduce Create a binary file: $> echo "Hello!" | gzip -c > test.gz Create an instance with a binary via Terraform: resource "incus_instance" "example" { name = "my-project" file { content = file("test.gz") target_path = "/test.gz" uid = 0 gid = 0 mode = "0700" create_directories = true } } Run terraform apply: ╷ │ Error: Error in function call │ │ on main.tf line 35, in resource "incus_instance" "example": │ 35: content = file("test.gz") │ ├──────────────── │ │ while calling file(str)

📅 Opened May 17, 2026💬 6 comments
Quality: 60/100Contribute

Description When modifying an existing incus_project resource to enable storage buckets (features.storage.buckets = "true"), terraform plan reports the change as valid and produces a clean diff. However, terraform apply fails because Incus does not allow modifying project feature flags on non-empty projects. The provider should detect this condition at plan time and produce a meaningful error, rather than allowing the plan to succeed and failing at apply. Steps to Reproduce Create a project with resources (instances, profiles, networks, etc.) via Terraform: resource "incus_project" "example" { name = "my-project" config = { "features.images" = "true" "features.networks" = "true" "features.networks.zones" = "true" "features.profiles" = "true" "features.storage.volumes" = "true" } } # ... instances and other resources in the project ... Add storage buckets to the project config: config = { # ... existing features ... "feat

📅 Opened Mar 31, 2026💬 0 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 lxc/terraform-provider-incus

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

Frequently Asked Questions - Contributing to lxc/terraform-provider-incus

01

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

lxc/terraform-provider-incus 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.

02

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

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

03

What does the 58.3 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 58.3 places lxc/terraform-provider-incus in the Welcoming tier.

04

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

The external pull request merge rate is 94.4%. 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 lxc/terraform-provider-incus?

Yes, lxc/terraform-provider-incus currently has 2 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 lxc/terraform-provider-incus 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.