johannesjo/parallel-code - Open Source PR Review Scorecard

Run Claude Code, Codex, and Gemini side by side — each in its own git worktree

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

External PR Merge Rate: 70%

Response Time: -

First Timer Success: 80%

Frequently Asked Questions

Is johannesjo/parallel-code welcoming to first-time open-source contributors?

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

What does the 66.5 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 66.5 places johannesjo/parallel-code in the A tier.

What is the external contributor pull request merge rate for johannesjo/parallel-code?

The external contributor pull request merge rate for johannesjo/parallel-code is 69.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in johannesjo/parallel-code?

johannesjo/parallel-code currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

johannesjo
johannesjo/parallel-codeA•Welcoming1.0k
GitHub
Back to Explorer
johannesjo

johannesjo/parallel-code

1,042
InactiveA•Welcoming(66/100)TypeScript

Run Claude Code, Codex, and Gemini side by side — each in its own git worktree

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.4/10
Patience Score
8.4/10
Nitpick Rate
45%

Highly welcoming maintainers in johannesjo/parallel-code. 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
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
69.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
80.0%
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
69.6%
Merge Gauge
80.0%
1st-Timer
Community Vibe52/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Why Parallel Code is a great home for more model choice Parallel Code runs AI coding CLIs — Claude Code, Codex, Gemini, Copilot, Antigravity — side by side, each task in its own git worktree and branch. That automatic isolation removes the merge conflicts that normally cap how many parallel agents one developer can safely run; the reviewable diffs you merge or toss are the payoff. Ask Code already makes the model behind a question configurable — Claude Code by default or MiniMax M2.7, called as a direct chat/completions endpoint with a Bearer API key set in Settings. A gateway serving many models through one endpoint would let those users pick the right model per question instead of re-pointing provider config each time. Proposal: OrcaRouter as an optional Ask Code provider I'm an engineer on the OrcaRouter team. This is a proposal for maintainer feedback, not finished code — nothing is implemented or tested yet. The seam is electron/ipc/ask-code.ts, where AskCodeProvider is cu

📅 Opened Sep 5, 2026💬 4 comments
Quality: 65/100Contribute

Summary Running the packaged v1.14.1 build on macOS with Claude Code as the agent, the sidebar "waiting for you" tray never appeared while a task sat blocked on a permission dialog. The tray is the pinned group under the New Task button (NeedsInputTray, src/components/Sidebar.tsx:290). I have not root-caused it. This is a write-up of what has been ruled out, so whoever picks it up doesn't repeat the elimination. Ruled out The feature is present in the release. src/store/sidebar-attention.ts exists at both v1.14.0 and v1.14.1 (checked via the contents API). An earlier conclusion that the feature was unmerged was wrong — it came from testing containment against a local main that was 27 commits behind upstream/main. The setting is on. sidebarNeedsInputFirst defaults to true (src/store/core.ts:53), and persistence falls back to true when the key is absent (src/store/persistence.ts:511). The actual persisted value in ~/Library/Application Support/parallel-code/state.json on the affected m

📅 Opened Aug 12, 2026💬 1 comment
Quality: 40/100Contribute

Environment: Parallel Code 1.12.0 (deb), Linux (X11, GNOME). Code references verified against main @ d000fff65. Problem The horizontal scrollbar under the task strip is very hard to hit What happens: The scrollbar itself is a 5px sliver. Aiming at it takes real care. Miss it by a few pixels upward and the cursor turns into the col-resize double-arrow (↔ with the vertical bar), which doesn't actually work Likely cause The col-resize zone is the panel resize handles (src/styles.css): .resize-handle-h { width: 6px; cursor: col-resize; } Requests Make the strip's horizontal scrollbar a drag target Keep the resize handles clear of the scrollbar band, so the bottom strip of the strip is actually scroll

📅 Opened Aug 8, 2026💬 0 comments
Quality: 40/100Contribute

All small, independently fixable, and verified against the code. Checklist form so they can be picked off one at a time (several are good first issues): Setting label says "on merge" but acts on close. "Always delete branch and worklog on merge" (EditProjectDialog.tsx:348) toggles deleteBranchOnClose, whose only readers are close paths (tasks.ts:417, TaskPanel.tsx:598, CloseTaskDialog.tsx:99); the merge path uses a separate cleanupAfterMerge checkbox. Also "worklog" is presumably "worktree". Worktree path clips without ellipsis. TaskBranchInfoBar.tsx:247 renders the full path inside a nested inline-flex <button>; the InfoBar's declared text-overflow: ellipsis (InfoBar.tsx:33-35) can't apply to a nested flex child, so long paths clip hard. Abbreviate with the ~-shortening already used in the sidebar and put the full path in the tooltip. Dead overlay rule. .dialog-overlay background in styles.css:1363 (44% black) is always overridden by the inline rgba(0,0,0,0.55) in Dialog.tsx:94

📅 Opened Jul 7, 2026💬 0 comments
Quality: 80/100Contribute

Problem There is no icon module: 75 inline <svg> blocks across 31 files, with heavy duplication and mixed media. The Octicon close path (M3.72 3.72…) is hand-pasted 10 times; copy/branch and external-link paths several times each; the folder icon exists in two subtly different variants that render visibly differently. Text glyphs serve as icons alongside SVGs: ✕ (SubTaskStrip.tsx:74, CommitTreeOverlay.tsx:149, TerminalSearchOverlay.tsx:150), ✓ (SubTaskStrip.tsx:236, TaskStepsSection.tsx:231), ❯ throughout PromptInput.tsx, and an emoji 📁 (NewTaskDialog.tsx:1093) — emoji render platform-dependently and full-color, breaking the otherwise monochrome currentColor icon language. Icon sizes span ~9 distinct widths (8–16 px). Proposed fix A single src/components/icons.tsx exporting the ~20 actual glyphs as components with a size prop (16 default, 12 small), then replace the pasted SVGs and glyph/emoji icons. Mechanical work, good first issue. From a full design/UX audit (2026

📅 Opened Jul 7, 2026💬 1 comment
Quality: 80/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 johannesjo/parallel-code

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

Frequently Asked Questions - Contributing to johannesjo/parallel-code

01

Is johannesjo/parallel-code welcoming to first-time open-source contributors?

johannesjo/parallel-code has a recorded first-timer success rate of 80.0%. 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 66.5 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 66.5 places johannesjo/parallel-code in the Welcoming tier.

04

What is the external contributor pull request merge rate for johannesjo/parallel-code?

The external pull request merge rate is 69.6%. 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 johannesjo/parallel-code?

Yes, johannesjo/parallel-code currently has 6 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 johannesjo/parallel-code 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.