Backstitch: Real-Time Version Control for Godot
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 78%
Response Time: -
First Timer Success: 100%
inkandswitch/backstitch has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in inkandswitch/backstitch 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.
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 65.9 places inkandswitch/backstitch in the A tier.
The external contributor pull request merge rate for inkandswitch/backstitch is 77.8%, based on public PR activity from non-core contributors.
inkandswitch/backstitch currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in inkandswitch/backstitch. Ensure PR scope matches issue requirements closely before requesting review.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/inkandswitch/backstitch?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (35% approval). Keep your diff compact for rapid review.
We should add an HTTP Basic authentication mode. A proof of concept using the insecure URL pattern is here: #337 A real implementation of this should NOT support the URL syntax, because the URL is stored insecurely. Instead: Implement an HTTP Basic authenticator alongside OIDC "auth":"basic" in describe on the Sync Server; implement that mode on the server/Docker Alter dialer.rs to use a Basic authentication header (similar to the proof-of-concept) Add a popup UI box with basic username and password to the authentication flow, similar to OIDC Store the password securely in the system keychain
Currently I believe the list of servers offered in this menu: is stored only in backstitch.cfg [backstitch]available_servers in each project. If I have used https://backstitch.endlessstudios.com/ in one project, it is likely that I would like to use it in another project. Perhaps this list could be stored in the editor settings rather than in backstitch.cfg?
@jgbourque tells me that he has seen on some number of occasions people running backstitch-launcher but then forgetting to actually create a project before they start work. Later they are surprised that they can't revert a recent change. When I first open a Backstitch project, the top bar has a branch indicator showing "main": If I click the "Backstitch" tab, while all the buttons at the top are desaturated a bit, the sync status icon still shows ✔️ : If you scroll down then you see the instructions that tell you how to actually join/create a Backstitch project. I think the top bar should, instead of the misleading "main" branch picker, show something like: [⚠️ no project] Clicking it could focus the Backstitch sidebar. Then the sync indicator in the Backstitch sidebar could also show a more neutral icon when no project is configured.
Needs testing. Someone reported that a change from x.gd to X.gd wasn't tracked.
When Backstitch changes a visual node file, the editor doesn't reload.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to inkandswitch/backstitch, 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 inkandswitch/backstitch acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.8% were successfully merged into the primary branch.
inkandswitch/backstitch has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 65.9 places inkandswitch/backstitch in the Welcoming tier.
The external pull request merge rate is 77.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, inkandswitch/backstitch currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for inkandswitch/backstitch 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.