The self-hosted AI workflow automation platform for Git repositories.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 81%
Response Time: 3d
First Timer Success: 63%
tmseidel/ai-git-bot has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tmseidel/ai-git-bot respond to incoming external pull requests in approximately 66.1 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 67.1 places tmseidel/ai-git-bot in the A tier.
The external contributor pull request merge rate for tmseidel/ai-git-bot is 80.5%, based on public PR activity from non-core contributors.
tmseidel/ai-git-bot does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in tmseidel/ai-git-bot. 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/tmseidel/ai-git-bot?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~43 hours (96% approval). Large PRs (>500 lines) take ~317 hours (36% approval). Keep your diff compact for rapid review.
I just got a "Broken pipe" error message while an agentic review was running. Most likely short lived network problems. This is the method in question: ai-git-bot/src/main/java/org/remus/giteabot/agent/loop/AgentLoop.java Lines 341 to 367 in 86cce05 private ChatTurn callAiWithRetry(List<AiMessage> history, String currentMessage, List<ToolDescriptor> tools, String systemPrompt, ToolingMode resolvedMode) { int maxRetries = 2; for (int attempt = 1; attempt <= maxRetries; attempt++) { try { if (resolvedMode == ToolingMode.NATIVE) {
Right now the paginated lists in the usage log only have buttons to jump to the next or previous page: So if I want to look at the logs of a workflow spanning 50+ rounds, I have to click around a lot. Would it be possible to add buttons to jump to the first / last page? and Add a dropdown (or similar) to choose the amount of elements on each page of the list Maybe an input to jump to a specific page could be added - or show the next few page numbers. For example, what I had in mind: This also affects other paginated list then only the usage log. E.g. mcp selection, tool selection, etc. Only to a lesser effect on those lists, since fewer elements are ever present in them.
Today I added context7 to my configuration. This mcp requires an api key. The only way (that I could find) to configure the api key was to input it as plain text into the mcp config. Idea: Either: add the possibility to expand environment variables in the mcp config. Or add hashicorp vault support, and support expansion of vault paths/keys in the mcp config. Any of these two would suffice as a first step.
Right now the mcp config is a simple textarea. This works fine when entering a single or maybe 2 mcp configs. Some ideas to improve it: Add line numbers on the left side of the editor panel. Add a button to pretty print the config. This would replace the current coontent of the text area with a pretty printed version of the json When saving an invalid json, a generic error message is shown. However, at least jackson provides detailed information at which line number and position the error occured. Could this also be shown.
I faced a few issues while adding litelllm. So I'm adding the litelllm support to contribute to the project. Also with a bugfix with the secret key
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 tmseidel/ai-git-bot, 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 tmseidel/ai-git-bot acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 80.5% were successfully merged into the primary branch.
tmseidel/ai-git-bot has a recorded first-timer success rate of 62.5%. 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 67.1 places tmseidel/ai-git-bot in the Welcoming tier.
The external pull request merge rate is 80.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
tmseidel/ai-git-bot does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for tmseidel/ai-git-bot 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.