Windows/macOS/Linux GUI client for GIT users
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 57%
Response Time: 2d
First Timer Success: 56%
sourcegit-scm/sourcegit has a recorded first-timer success rate of 55.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in sourcegit-scm/sourcegit respond to incoming external pull requests in approximately 58.3 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 62.9 places sourcegit-scm/sourcegit in the A tier.
The external contributor pull request merge rate for sourcegit-scm/sourcegit is 57.4%, based on public PR activity from non-core contributors.
sourcegit-scm/sourcegit currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in sourcegit-scm/sourcegit. Maintains strict focus on technical quality and test standards.
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/sourcegit-scm/sourcegit?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~38 hours (72% approval). Large PRs (>500 lines) take ~280 hours (26% approval). Keep your diff compact for rapid review.
Summary When the number of staged files exceeds the visible area, the Staged files list does not render all items even though a scrollbar appears. Scrolling works correctly in the Unstaged list but not in the Staged list. This results in an incomplete/partially rendered Staged files list and prevents accessing items beyond the initial viewport. Steps to reproduce Create a new repository Generate files ( in my case 20 ) Stage all files Scroll the staged list Expected Behaviour Same as on the unstaged panel/list Scrollbar is displayed if number of files exeed display space Actual Behaviour The staged list shows a scrollbar but is not rendering the full list If the panel is resized so all items fit without scrolling, all files are displayed Details Version: 2026.12 Source revision: d67c995 OS: Debian 13.5
There isn't a single key for the symbol on the keyboard. I have to press Alt Gr+7 to input the symbol. So when I press the combination Ctrl+Alt Gr+7, the terminal doesn't open. Please change to something else, for example Alt+T.
Hi, I just started to use AI to generate the commit message inside SourceGit. I found that after the AI generates the commit I cannot edit it, until i do something, like the focus was blocked, I tried that for example if I open the window of conventional commits, I can write something or delete it. But if I change the branch, copy/paste with the mouse, or do any other thing I am not able to do it. I recorded a video, but you have to trust that when I don't write or delete anything is because it does not works 😄 Screenshare.-.2026-03-11.12_27_47.PM.mp4 System: PopOS 24.04 LTS SourceGit Version: 2026.05
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 sourcegit-scm/sourcegit, 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 sourcegit-scm/sourcegit acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 57.4% were successfully merged into the primary branch.
sourcegit-scm/sourcegit has a recorded first-timer success rate of 55.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 62.9 places sourcegit-scm/sourcegit in the Welcoming tier.
The external pull request merge rate is 57.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sourcegit-scm/sourcegit currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for sourcegit-scm/sourcegit 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.