A CLI for interacting with Tekton!
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 74%
Response Time: 2d
First Timer Success: 71%
tektoncd/cli has a recorded first-timer success rate of 71.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tektoncd/cli respond to incoming external pull requests in approximately 40.4 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 58.1 places tektoncd/cli in the A tier.
The external contributor pull request merge rate for tektoncd/cli is 73.6%, based on public PR activity from non-core contributors.
tektoncd/cli currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in tektoncd/cli. 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/tektoncd/cli?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~26 hours (92% approval). Large PRs (>500 lines) take ~194 hours (33% approval). Keep your diff compact for rapid review.
Feature request tkn pipelinerun logs does not follow child PipelineRuns created by the Pipelines-in-Pipelines (PinP) feature. When a PipelineTask uses pipelineSpec or pipelineRef, the parent PipelineRun owns a child PipelineRun, not a TaskRun. tkn pipelinerun logs only discovers TaskRuns, so TaskRuns inside child PipelineRuns are invisible. Inline pipelineSpec is already functional today, and tektoncd/pipeline#9432 adds pipelineRef support, making PinP a fully functional alpha feature (TEP-0056). In both cases, tkn cannot surface the child PipelineRun TaskRun logs. Use case Apply the following resources (enable-api-fields must be set to alpha): apiVersion: tekton.dev/v1 kind: Pipeline metadata: name: parent-pipeline spec: tasks: - name: call-child pipelineSpec: tasks: - name: greet taskSpec: steps: - name: echo image: busybox script: echo "Hello from child" --- apiVersion: tekt
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 tektoncd/cli, 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 tektoncd/cli acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.6% were successfully merged into the primary branch.
tektoncd/cli has a recorded first-timer success rate of 71.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 58.1 places tektoncd/cli in the Welcoming tier.
The external pull request merge rate is 73.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tektoncd/cli currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for tektoncd/cli 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.