My Computer for Nautilus, what GNOME Files should have always been
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 73%
Response Time: 6h
First Timer Success: 58%
yannmasoch/nautilus-my-computer has a recorded first-timer success rate of 58.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in yannmasoch/nautilus-my-computer respond to incoming external pull requests in approximately 5.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 52.3 places yannmasoch/nautilus-my-computer in the B tier.
The external contributor pull request merge rate for yannmasoch/nautilus-my-computer is 73.3%, based on public PR activity from non-core contributors.
yannmasoch/nautilus-my-computer currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in yannmasoch/nautilus-my-computer welcoming community pull requests and bug fixes.
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/yannmasoch/nautilus-my-computer?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (92% approval). Large PRs (>500 lines) take ~28 hours (33% approval). Keep your diff compact for rapid review.
Follow-up to #35. A Reddit user reported the flake install steps from #35 didn't work for them (source: https://www.reddit.com/r/gnome/comments/1v43z1l/comment/p6o3twp/): I've tried following the steps to install it from a flake based on the information found on the project GitHub, but have had no luck. Might I suggest taking a look at OpenLogi's section on NixOS installation, here? As someone who is entirely new to flakes, this is the best example I've found of showing the user exactly what they need to do to get a piece of software on their system via a flake. If you need someone with a NixOS machine to help test the flake setup, I'm available.
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 yannmasoch/nautilus-my-computer, 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 yannmasoch/nautilus-my-computer acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.3% were successfully merged into the primary branch.
yannmasoch/nautilus-my-computer has a recorded first-timer success rate of 58.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 52.3 places yannmasoch/nautilus-my-computer in the Solid tier.
The external pull request merge rate is 73.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, yannmasoch/nautilus-my-computer 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 yannmasoch/nautilus-my-computer 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.