Flutter Plugin for IntelliJ
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 87%
Response Time: 19h
First Timer Success: 75%
flutter/flutter-intellij 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.
Maintainers in flutter/flutter-intellij respond to incoming external pull requests in approximately 18.9 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.5 places flutter/flutter-intellij in the A tier.
The external contributor pull request merge rate for flutter/flutter-intellij is 86.8%, based on public PR activity from non-core contributors.
flutter/flutter-intellij currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in flutter/flutter-intellij. Prompt code reviews with positive guidance for new contributors.
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/flutter/flutter-intellij?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (96% approval). Large PRs (>500 lines) take ~91 hours (39% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Java.
Countly Digital Analytics Android SDK
🔥LeetCode solutions in any programming language | 多种编程语言实现 LeetCode、《剑指 Offer（第 2 版）》、《程序员面试金典（第 6 版）》题解
Ultimate Component Suite for Jakarta Faces
Summary If a project's Flutter SDK path doesn't resolve, the plugin runs its "Fixing Flutter module configuration" path on project open and deadlocks the IDE permanently — no error, no timeout, process kill required. setFlutterModuleWithoutReload calls ProjectImpl.save() from inside a write action on the EDT. That save dispatches document saving to a worker, then parks the EDT in a nested modal pump waiting for it; the worker must call back into the EDT to fire beforeAllDocumentsSaving. Circular wait, write lock held throughout. Same EDT/Semaphore pattern as #9013 and #9055, different call site — those were FlutterSettingsConfigurable, this is project open. Both closed against 2026.1; this reproduces on 2026.2 / plugin 95.0.0. The invalid SDK path is only the trigger; the deadlock is a re-entrancy bug and is not FVM-specific. Environment Plugin 95.0.0 · IntelliJ IDEA 2026.2 (IU-262.9437.185) · JVM 25.0.3 · Windows 11 10.0.26200 · Flutter 3.47.1 stable / Dart 3.13.1 Reproduction
Description Every hot reload and hot restart triggers a "Reloading..." entry in the IDE Notifications panel (bell icon). Over a typical development session, these accumulate rapidly in the Timeline view, cluttering the panel and burying genuinely important notifications (e.g., "Shortcuts conflicts"). Steps to Reproduce Open any Flutter project in Android Studio Run the app in debug mode Make changes and trigger hot reload/restart multiple times (Cmd+S or toolbar) Open the Notifications panel (bell icon, top-right) Expected Behavior Hot reload/restart events should either: Not appear in the Notifications timeline at all (they are transient progress events, not persistent alerts), OR Be grouped/collapsed into a single entry per session, OR Use a lower-priority notification level that doesn't persist in timeline Actual Behavior Each hot reload adds a separate "Reloading..." entry to the Notifications timeline. In a single session, 4–10+ entries accumulate, pushing critical notificat
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 flutter/flutter-intellij, 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 flutter/flutter-intellij acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.8% were successfully merged into the primary branch.
flutter/flutter-intellij 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.
The initial maintainer response time averages ~18 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.5 places flutter/flutter-intellij in the Welcoming tier.
The external pull request merge rate is 86.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, flutter/flutter-intellij currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for flutter/flutter-intellij 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.