floatpane/matcha - Open Source PR Review Scorecard

A beautiful and functional email client for your terminal, built with Go and the charming Bubble Tea TUI library. Never leave your command line to check your inbox or send an email again!

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

External PR Merge Rate: 79%

Response Time: 5d

First Timer Success: 58%

Frequently Asked Questions

Is floatpane/matcha welcoming to first-time open-source contributors?

floatpane/matcha has a recorded first-timer success rate of 57.9%. 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 floatpane/matcha respond to incoming external pull requests in approximately 110.8 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 62.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 62.3 places floatpane/matcha in the A tier.

What is the external contributor pull request merge rate for floatpane/matcha?

The external contributor pull request merge rate for floatpane/matcha is 79.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in floatpane/matcha?

floatpane/matcha currently has 37 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

floatpane
floatpane/matchaA•Welcoming1.1k
GitHub
Back to Explorer
floatpane

floatpane/matcha

1,110
InactiveA•Welcoming(62/100)Go

A beautiful and functional email client for your terminal, built with Go and the charming Bubble Tea TUI library. Never leave your command line to check your inbox or send an email again!

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
8.4/10
Patience Score
8.6/10
Nitpick Rate
25%

Highly welcoming maintainers in floatpane/matcha. 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
4 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
79.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
8 core
Highly collaborative maintainer core
Diagnostic Health HUD
79.4%
Merge Gauge
57.9%
1st-Timer
Community Vibe49/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Is your feature request related to a problem? No response Describe the solution you'd like Parse the Gmail reactions, as an emoji with a number at the bottom of the screen and add an ability to react to emails. This is simple, as the reactions are sent as a regular email with the emoji. Describe alternatives you've considered No response Additional context No response

📅 Opened Jun 23, 2026💬 1 comment
Quality: 70/100Contribute

Is your feature request related to a problem? New users don't discover keybindings for the current view. Describe the solution you'd like Show a compact, context-aware hint bar of the most relevant keybindings. Describe alternatives you've considered Memorizing the docs. Additional context Beginner friendly. Pull from config/keybinds.go; render in the relevant tui/ views.

📅 Opened Jun 21, 2026💬 1 comment
Quality: 80/100Contribute

Is your feature request related to a problem? CC may always be shown or always hidden; users want to toggle it. Describe the solution you'd like Add a config option and settings to show/hide the CC field in the composer. Describe alternatives you've considered Always-on CC field. Additional context Beginner friendly. See tui/composer.go.

📅 Opened Jun 21, 2026💬 1 comment
Quality: 70/100Contribute

Is your feature request related to a problem? The signature settings screen doesn't preview the rendered signature. Describe the solution you'd like Render a live preview of the configured signature in settings. Describe alternatives you've considered Sending a test email. Additional context Beginner friendly. See tui/settings_general.go and config/signature.go.

📅 Opened Jun 21, 2026💬 1 comment
Quality: 55/100Contribute

Is your feature request related to a problem? There's no way to enable/disable a notification sound. Describe the solution you'd like Add a config toggle for playing a sound on new-mail notifications. Describe alternatives you've considered OS notification settings. Additional context Beginner friendly. See notify/notify.go.

📅 Opened Jun 21, 2026💬 1 comment
Quality: 55/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 floatpane/matcha

When evaluating whether to contribute to floatpane/matcha, 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 floatpane/matcha acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to floatpane/matcha

01

Is floatpane/matcha welcoming to first-time open-source contributors?

floatpane/matcha has a recorded first-timer success rate of 57.9%. 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 ~4 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 62.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 62.3 places floatpane/matcha in the Welcoming tier.

04

What is the external contributor pull request merge rate for floatpane/matcha?

The external pull request merge rate is 79.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 floatpane/matcha?

Yes, floatpane/matcha currently has 37 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 floatpane/matcha 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.