Declarative Continuous Deployment for Kubernetes
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 48%
Response Time: -
First Timer Success: 47%
argoproj/argo-cd has a recorded first-timer success rate of 46.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in argoproj/argo-cd 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 63.4 places argoproj/argo-cd in the A tier.
The external contributor pull request merge rate for argoproj/argo-cd is 47.9%, based on public PR activity from non-core contributors.
argoproj/argo-cd currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in argoproj/argo-cd. 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/argoproj/argo-cd?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (60% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
Checklist: I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq. I've included steps to reproduce the bug. I've pasted the output of argocd version. Describe the bug Badges generated for short revisions are too wide, 400px, which can make them wider than badges that contain more text. To Reproduce Get a badge using/api/badge?name=<app>&revision=true with a revision that is equal to or less than 7 characters. A specific example is Helm chart version 5.20.2. Expected behavior The badge has the appropriate width of 192px, as per the docs. Screenshots Version argocd: v3.4.5 Logs Paste any relevant application logs here.
Checklist: I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq. I've included steps to reproduce the bug. I've pasted the output of argocd version. Describe the bug To Reproduce Load https://cd.apps.argoproj.io/applications/argocd/argo-cd?resource=kind%3AConfigMap%2Cname%3Aargocd-cm&view=pods&node=%2FPod%2Fargocd%2Fargocd-application-controller-0&tab=logs Hover over the quill Expected behavior Text shouldn't suggest selecting a pod when there's only one pod to look at Screenshots Version { "Version": "v3.6.0+b5fc12e", "BuildDate": "2026-08-13T10:22:54Z", "GitCommit": "b5fc12e0155c6a58c0924afc0ec68478cf25da11", "GitTreeState": "clean", "GoVersion": "go1.26.5", "Compiler": "gc", "Platform": "linux/amd64", "KustomizeVersion": "v5.8.1 2026-02-09T16:15:27Z", "HelmVersion": "v4.2.3+g43e8b7f", "KubectlVersion": "v0.36.1", "JsonnetVersion": "v0.22.0" } Logs Paste any relevant application logs here.
Summary Follow-up to #26651. That PR adds a list of not-ready resources to the argocd app wait timeout error, capped at 10 entries (with a ... and N more suffix) so the message stays readable. The cap is currently a hard-coded constant (formatPendingResources). It would be more flexible to expose it as a command flag (e.g. --max-pending-resources) so operators with large applications can see more (or fewer) entries. Notes The 10-entry default keeps the current behavior. The flag would touch the waitOnApplicationStatus call sites (wait, sync, sync --operation), so it was kept out of #26651 to limit that PR's scope. Raised at the request of a reviewer on #26651 to track the // TODO left in the code.
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 argoproj/argo-cd, 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 argoproj/argo-cd acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 47.9% were successfully merged into the primary branch.
argoproj/argo-cd has a recorded first-timer success rate of 46.8%. 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 63.4 places argoproj/argo-cd in the Welcoming tier.
The external pull request merge rate is 47.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, argoproj/argo-cd currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for argoproj/argo-cd 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.