---
# System prepended metadata

title: Untitled

---

TL;DR: adoption of [`pipelines-as-code`](https://github.com/openshift-pipelines/pipelines-as-code/) in the `tektoncd` org (https://pipelinesascode.com/).

The [`pipelines-as-code`](https://github.com/openshift-pipelines/pipelines-as-code/) propose an opinionated CI based on OpenShift Pipelines / Tekton. Its goal is to let you define your [Tekton](https://tekton.dev/) templates inside your source code repository and have the pipeline run and report the status of the execution when triggered by a Pull Request or a Push.

Some notably features of [`pipelines-as-code`](https://github.com/openshift-pipelines/pipelines-as-code/):

- Pull-request status support: When iterating over a Pull Request. Statuses and Control is done on GitHub.
- GitHub Checks API support to set the status of a PipelineRun including rechecks
- GitHub Pull Request and Push event support
- Pull-request “GitOps” actions through comments with /retest, /test <pipeline-name> and so on.
- Automatic Task resolution in Pipelines (local Tasks, Tekton Hub, and remote URLs) — Note: This *predates* tektoncd/pipelines resolvers, and will slowly but surely be replaced by built-in resolvers as users will adopt those resolvers.
- Efficient use of GitHub blobs and objects API for retrieving configurations
- Git events Filtering and support for separate pipelines for each event
- Gitlab, Bitbucket Server, Bitbucket Cloud and GitHub Webhook support.
- `tkn-pac` plug-in for Tekton CLI for managing pipelines-as-code repositories and bootstrapping.

It is currently shipped with OpenShift Pipelines but it is released independently. It is also working and tested on vanilla kubernetes and has nothing OpenShift specific in the code.

The proposal is to have `pipelines-as-code` hosted and maintained by the community, and help shape the next set of Tektoncd components.

## Who will own it

- @vdemeester 
- @chmouel 
- @sm43 
- @savitaashture 
- *[any other takers]*