tsuyoshicho/action-textlint - Open Source PR Review Scorecard

Run textlint with reviewdog on pull requests to improve document writing experience.

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

External PR Merge Rate: 97%

Response Time: 1d

First Timer Success: 100%

Frequently Asked Questions

Is tsuyoshicho/action-textlint welcoming to first-time open-source contributors?

tsuyoshicho/action-textlint 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 tsuyoshicho/action-textlint respond to incoming external pull requests in approximately 29.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 71.2 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 71.2 places tsuyoshicho/action-textlint in the B tier.

What is the external contributor pull request merge rate for tsuyoshicho/action-textlint?

The external contributor pull request merge rate for tsuyoshicho/action-textlint is 96.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in tsuyoshicho/action-textlint?

tsuyoshicho/action-textlint does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

tsuyoshicho
tsuyoshicho/action-textlintBSolid73
GitHub
Back to Explorer
tsuyoshicho

tsuyoshicho/action-textlint

73
BSolid(71/100)Shell

Run textlint with reviewdog on pull requests to improve document writing experience.

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%

Growing Shell project in tsuyoshicho/action-textlint welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • Ensure code complies with Shell style conventions
  • Keep PRs scoped 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
1 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
96.7%
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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
96.7%
Merge Gauge
100.0%
1st-Timer
Community Vibe77/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for tsuyoshicho/action-textlint.

View all good first issues directly on GitHub

Looking for more Shell beginner tasks?Explore Shell 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 tsuyoshicho/action-textlint

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

Frequently Asked Questions - Contributing to tsuyoshicho/action-textlint

01

Is tsuyoshicho/action-textlint welcoming to first-time open-source contributors?

tsuyoshicho/action-textlint 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 ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.2 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 71.2 places tsuyoshicho/action-textlint in the Solid tier.

04

What is the external contributor pull request merge rate for tsuyoshicho/action-textlint?

The external pull request merge rate is 96.7%. 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 tsuyoshicho/action-textlint?

tsuyoshicho/action-textlint 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 tsuyoshicho/action-textlint 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.