Google Chrome, Firefox, Opera and Microsoft Edge extension for reading news from RSS aggregator Feedly
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 76%
Response Time: <1h
First Timer Success: 100%
olsh/Feedly-Notifier 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.
Maintainers in olsh/Feedly-Notifier respond to incoming external pull requests in approximately 0.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 58.9 places olsh/Feedly-Notifier in the A tier.
The external contributor pull request merge rate for olsh/Feedly-Notifier is 76.5%, based on public PR activity from non-core contributors.
olsh/Feedly-Notifier currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Google Chrome, Firefox, Opera and Microsoft Edge extension for reading news from RSS aggregator Feedly
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in olsh/Feedly-Notifier.
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/olsh/Feedly-Notifier?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~4 hours (34% approval). Keep your diff compact for rapid review.
Split out of #246, which bundled three unrelated requests. Now that the extension has a sidebar on Firefox (sidebar_action, #386) and a side panel on Chromium (side_panel, #356), there is no way to open either from the keyboard. src/manifest.json declares no commands key at all. Firefox exposes _execute_sidebar_action as a special shortcut, so declaring it in commands gives users a bindable (and optionally default) shortcut in Manage Extension Shortcuts. Chromium has no _execute_side_panel equivalent, so it needs a normal named command whose handler calls the same code path the toolbar click uses to open the panel. Both branches would go behind the usual // @if BROWSER=... preprocessing, since the two halves are not interchangeable. Worth checking whether a default binding is a good idea at all, or whether the command should ship unbound and let users assign it — extensions that claim a default chord tend to collide with each other.
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 olsh/Feedly-Notifier, 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 olsh/Feedly-Notifier acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.5% were successfully merged into the primary branch.
olsh/Feedly-Notifier 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.
The initial maintainer response time averages ~<1 hour. 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 58.9 places olsh/Feedly-Notifier in the Welcoming tier.
The external pull request merge rate is 76.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, olsh/Feedly-Notifier 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 olsh/Feedly-Notifier 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.