pret/pokepinballrs - Open Source PR Review Scorecard

Decompilation of Pokémon Pinball: Ruby & Sapphire

C-Rank Grade: B (Solid) - 48/100

External PR Merge Rate: 100%

Response Time: 11d

First Timer Success: 100%

Frequently Asked Questions

Is pret/pokepinballrs welcoming to first-time open-source contributors?

pret/pokepinballrs has a recorded first-timer success rate of 100.0%. Repositories ranked B 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 pret/pokepinballrs respond to incoming external pull requests in approximately 261.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 48.0 C-Rank™ score (B 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 48.0 places pret/pokepinballrs in the B tier.

What is the external contributor pull request merge rate for pret/pokepinballrs?

The external contributor pull request merge rate for pret/pokepinballrs is 100.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in pret/pokepinballrs?

pret/pokepinballrs does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

pret
pret/pokepinballrsB•Solid138
GitHub
Back to Explorer
pret

pret/pokepinballrs

138
Active (30d)B•Solid(48/100)Low Sample (<20 PRs)ASAssembly

Decompilation of Pokémon Pinball: Ruby & Sapphire

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in pret/pokepinballrs welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
10 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
100.0%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
100.0%
Merge Gauge
100.0%
1st-Timer
Community Vibe70/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

This will likely involve a new set of values in the defines file, to coordinate how the tool is addressing into that memory space. - Sizes and raw memory positioning seems to be different than the defined funcs currently present. (I believe those were initially pulled from the emerald decomp?)

📅 Opened Jul 20, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more Assembly beginner tasks?Explore Assembly 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 pret/pokepinballrs

When evaluating whether to contribute to pret/pokepinballrs, 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 pret/pokepinballrs acknowledge new external contributions in approximately 10 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.

Frequently Asked Questions - Contributing to pret/pokepinballrs

01

Is pret/pokepinballrs welcoming to first-time open-source contributors?

pret/pokepinballrs has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 ~10 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 48.0 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 48.0 places pret/pokepinballrs in the Solid tier.

04

What is the external contributor pull request merge rate for pret/pokepinballrs?

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.

05

Are there beginner Good First Issues open in pret/pokepinballrs?

pret/pokepinballrs does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for pret/pokepinballrs 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.