unstablebuild/rune - Open Source PR Review Scorecard

the development environment for pros

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

External PR Merge Rate: 20%

Response Time: <1h

First Timer Success: -

Frequently Asked Questions

Is unstablebuild/rune welcoming to first-time open-source contributors?

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

What does the 56.2 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 56.2 places unstablebuild/rune in the A tier.

What is the external contributor pull request merge rate for unstablebuild/rune?

The external contributor pull request merge rate for unstablebuild/rune is 19.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in unstablebuild/rune?

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

unstablebuild
unstablebuild/runeA•Welcoming1.2k
GitHub
Back to Explorer
unstablebuild

unstablebuild/rune

1,241
Active (30d)A•Welcoming(56/100)Go

the development environment for pros

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

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

Highly welcoming maintainers in unstablebuild/rune. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in unstablebuild/rune focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Link the issue and include reproduction context in the PR
  • •Update docs or README when behavior changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not open context-free PRs
  • •Do not ship user-facing changes without matching docs
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

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

Merge Efficiency
19.5%
Selective 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
26 core
Highly collaborative maintainer core
Diagnostic Health HUD
19.5%
Merge Gauge
0.0%
1st-Timer
Community Vibe37/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Problem Rune Vim users have to retype every search term, especially painful when they are searching multiple times in a row. Proposed behavior Like in usual Vim, pressing up and down in search mode should toggle through previous/next search terms. Area Editor and text handling Alternatives considered No response Additional context No response Checks I searched existing issues and this is not a duplicate. I would be willing to work on this.

📅 Opened Oct 6, 2026💬 0 comments
Quality: 75/100Contribute

Problem windowconverttab requires a tab name: windowconverttab <name> [<icon>] Running it bare fails with command expects at least one argument with tab name (internal/ide/ex.go:1492). That forces users to invent a name every time they want to promote a window to a tab. The preset prompt-prefill bindings (echo {prompt}windowconverttab<space> in preset_modal.yaml, preset_helix.yaml, preset_standard_*.yaml) and the Window → Convert to Tab… menu entry leave the user at a prompt where pressing Enter without typing a name fails. Proposed behavior Make <name> optional. When it is omitted (or empty), name the tab with a random two-word petname, the same style Rune Agent uses for conversation IDs (e.g. rolling-fox): windowconverttab [<name> [<icon>]] windowconverttab → tab named e.g. brave-otter, default icon ``. windowconverttab build → tab named build, default icon (unchanged). windowconverttab build X → tab named build, icon X (unchanged). Setting a custom icon still requires

📅 Opened Sep 28, 2026💬 5 comments
Quality: 60/100Contribute

What happened In Rune cw acts like dw and drops to insert mode. However, in Vim outside of Rune the two behaviours are different: dw deletes the word and consumes the space after, while cw deletes until the end of the word like de and doesn't consume the space after, then drops to insert mode. What you expected Like in Vim, cw should delete until end of word only, then go to insert mode Steps to reproduce Try it out in the text editor. This is probably a good first issue. Area Editor and text handling Rune version v1.2.1-138-gc5aaac32 OS and architecture Ubuntu 24.04 Shell No response Logs, crash report, or screenshots Relevant configuration Checks I searched existing issues and this is not a duplicate. I can reproduce this on the latest released version.

📅 Opened Sep 28, 2026💬 1 comment
Quality: 75/100Contribute

Problem On Linux, Rune's GUI only speaks X11. Our ebiten fork (github.com/unstablebuild/ebiten/v2, currently v2.7.5-ub.32) vendors GLFW 3.3.8 and compiles only its X11 platform (internal/glfw/build_linux.go defines _GLFW_X11). On a Wayland session Rune always runs as an XWayland client, and inherits XWayland's limits: Scaling. X11 has no per-window scale; GLFW reads one global Xft.dpi. On fractional-scale monitors the compositor stretches Rune's 1x buffer, which blurs text (#55). A move to a monitor with a different scale can't be detected. Input goes through the X server: layouts through XKB groups, text through XIM, and the scroll wheel as discrete button clicks. Dependency. The GUI doesn't start without XWayland installed. Blurry fractional scaling is the most visible symptom, but fixing it means adding a Wayland platform to the fork and making Rune's GUI layer work with it. This issue scopes that work. Upstream context. ebiten had an opt-in -tags=wayland build on GLFW 3.3 and rem

📅 Opened Sep 25, 2026💬 1 comment
Quality: 35/100Contribute

What happened Going to the next word on a blank line does not move the cursor to the next line. What you expected Normal vim behaviour: Open a file with lines with an empty line between them (like the space between function definitions in a piece of code) Press w on the end of the line before the empty line, the cursor moves to the empty line Press w again, the cursor moves to the line below the empty line Move the cursor to the empty line, press w. The cursor moves to the line below the empty line Steps to reproduce Open a file with lines with an empty line between them (like the space between function definitions in a piece of code) Press w on the end of the line before the empty line, the cursor jumps to 2 lines below Move the cursor to the empty line, press w. Nothing happens Area Editor and text handling Rune version v1.2.1-105-g35db79f0 OS and architecture Ubuntu 24.04 Shell No response Logs, crash report, or screenshots Relevant configuration Checks I searched existing i

📅 Opened Sep 23, 2026💬 0 comments
Quality: 50/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 unstablebuild/rune

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

Frequently Asked Questions - Contributing to unstablebuild/rune

01

Is unstablebuild/rune welcoming to first-time open-source contributors?

unstablebuild/rune has a recorded first-timer success rate of 0.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 ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 56.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 56.2 places unstablebuild/rune in the Welcoming tier.

04

What is the external contributor pull request merge rate for unstablebuild/rune?

The external pull request merge rate is 19.5%. 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 unstablebuild/rune?

Yes, unstablebuild/rune currently has 15 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 unstablebuild/rune 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.