tektoncd/pipelines-as-code

Pipelines-as-Code for Tekton

Hosted by CD Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

tektoncd/pipelines-as-code has 200+ stars and 150+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 17 minutes ago
Added to GitGenius on October 12th, 2026
Created on April 6th, 2021
Open Issues & Pull Requests: 89 (+0)
GitHub issues: Enabled
Number of forks: 150
Total Stargazers: 220 (+0)
Total Subscribers: 11 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.8 hours
Mean response time: 165.7 days
90th percentile: 896.2 days
Tracked items: 239

Maintainer activity

13 people did triage or write work on this repository in the last 12 months.

At least 46% of pipelines-as-code's 13 maintainers work at Red Hat. 12 say where they work, and 6 of those are Red Hat.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 18% of issues opened in the past year have never received a reply. 44% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "bug" is answered fastest, typically in about 3 days, while "testing" waits about 12 months. 71% of issues opened in the past year have been closed, leaving a working backlog. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 78
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 695 days
Stale 30+ days: 73
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (82)
  • priority/medium (35)
  • feature (29)
  • priority/low (24)
  • good first issue (19)
  • refactoring (14)
  • testing (12)
  • providers (11)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Tekton Pipelines-as-Code is a CI/CD framework that enables you to define and run Tekton pipelines directly from your Git repository.

The tool solves the problem of managing CI/CD pipelines separately from source code by letting you store pipeline definitions as PipelineRun files in a `.tekton/` directory alongside your code. Pipelines are triggered by Git events and results are reported back as pull request checks. The framework supports multiple Git providers including GitHub, GitLab, Bitbucket Cloud and Data Center, and Forgejo through both native integrations and webhooks. It includes ChatOps commands for controlling pipeline execution from pull request comments, an inline resolver that bundles remote tasks before cluster submission, and automated housekeeping to prune old runs and cancel superseded executions.

Teams should adopt this tool if they run Tekton on Kubernetes and want pipelines versioned with their code rather than managed in a separate system. It suits projects that need multi-provider Git support and want to treat pipeline configuration as code subject to the same review and version control as application code. The tool is specifically designed as an opinionated framework for Tekton rather than a general-purpose CI/CD system.

The project maintains active end-to-end testing and code coverage tracking. Development activity shows consistent attention to both core functionality and operational concerns, with documentation covering installation, pipeline creation, repository configuration, GitOps workflows, and provider-specific setup across multiple Git platforms.