johnbillion/user-switching - Open Source PR Review Scorecard

Instant switching between user accounts in WordPress and WooCommerce.

C-Rank Grade: C (Moderate) - 36/100

External PR Merge Rate: 44%

Response Time: 8d

First Timer Success: -

Frequently Asked Questions

Is johnbillion/user-switching welcoming to first-time open-source contributors?

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

What does the 35.8 C-Rank™ score (C 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 35.8 places johnbillion/user-switching in the C tier.

What is the external contributor pull request merge rate for johnbillion/user-switching?

The external contributor pull request merge rate for johnbillion/user-switching is 44.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in johnbillion/user-switching?

johnbillion/user-switching does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

johnbillion
johnbillion/user-switchingCModerate201
GitHub
Back to Explorer
johnbillion

johnbillion/user-switching

201
CModerate(36/100)PHP

Instant switching between user accounts in WordPress and WooCommerce.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
22%

Balanced & professional review environment in johnbillion/user-switching. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • Add unit tests with >80% coverage for modified code paths
  • Use conventional commit messages and clean branch names
  • Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • Do not submit unlinked PRs without referencing an existing issue
  • Do not mix refactoring and feature logic into a single commit
  • Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
7 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
44.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
44.4%
Merge Gauge
0.0%
1st-Timer
Community Vibe18/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for johnbillion/user-switching.

View all good first issues directly on GitHub

Looking for more PHP beginner tasks?Explore PHP 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 johnbillion/user-switching

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

Frequently Asked Questions - Contributing to johnbillion/user-switching

01

Is johnbillion/user-switching welcoming to first-time open-source contributors?

johnbillion/user-switching has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate 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 ~7 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 35.8 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 35.8 places johnbillion/user-switching in the Moderate tier.

04

What is the external contributor pull request merge rate for johnbillion/user-switching?

The external pull request merge rate is 44.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 johnbillion/user-switching?

johnbillion/user-switching 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 johnbillion/user-switching 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.