F# language server using Language Server Protocol
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 100%
Response Time: 16d
First Timer Success: -
ionide/FsAutoComplete has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ionide/FsAutoComplete respond to incoming external pull requests in approximately 381.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 48.8 places ionide/FsAutoComplete in the B tier.
The external contributor pull request merge rate for ionide/FsAutoComplete is 100.0%, based on public PR activity from non-core contributors.
ionide/FsAutoComplete currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in ionide/FsAutoComplete. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in ionide/FsAutoComplete focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/ionide/FsAutoComplete?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~248 hours (96% approval). Large PRs (>500 lines) take ~1829 hours (45% approval). Keep your diff compact for rapid review.
Details I am building a non-IDE semantic client on top of FsAutoComplete. Existing FSAC primitives such as definition, references, workspace symbols, and diagnostics are already useful, but higher-level navigation would make F# codebases much easier to explore from LSP clients and coding agents. The two missing capabilities I would like to request are standard LSP-style support for: textDocument/implementation callHierarchy/prepare, callHierarchy/incomingCalls, and callHierarchy/outgoingCalls Desired behavior textDocument/implementation For F# symbols, return implementing locations for cases such as: interface type -> implementing types interface member -> concrete member implementations abstract member -> overrides/implementations Results should use the same URI/range conventions as existing FSAC definition/references responses. callHierarchy/* For F# functions and members, support: prepare call hierarchy item at a position incoming calls: callers grouped by enclosing function/me
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 ionide/FsAutoComplete, 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 ionide/FsAutoComplete acknowledge new external contributions in approximately 15 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
ionide/FsAutoComplete has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 days+. 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 48.8 places ionide/FsAutoComplete in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ionide/FsAutoComplete 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 ionide/FsAutoComplete 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.