Vincent Demeester vdemeester

Copilot code review instructions for tektoncd/pipeline

These instructions guide GitHub Copilot when reviewing pull requests in this repository. Tekton Pipelines provides Kubernetes-style CRDs (Task, TaskRun, Pipeline, PipelineRun, and others) with controllers built on Knative's reconciler framework, and images built/deployed with ko.

General

Respond in English and keep review comments concise and actionable.

Tekton Catalog — Health Report

Analyzed 308 primary manifests (task/pipeline/stepaction).

Baseline: tektoncd/catalog@8e41018c7a60 (8e41018c7a601d33f860f714d0b911dc05359af7) · Generated: 2026-06-08 (UTC) Scope: primary manifests only (<kind>/<name>/<version>/<name>.yaml); samples/tests excluded. CVE scan: trivy, severity HIGH+CRITICAL, default image per resource, digest-resolved where possible (50 distinct images; 4 unscannable due to old media types / removed images).

How to read this

tekton-oracle cluster — work streams analysis (2026-05-13)

Status: node `10.0.128.239` recovered ✅

Rebooted via OCI CLI, now Ready again. Still need Fluent Bit memory fix (100M → 256M).

1. PVC sprawl — 220 PVCs, only 5 in use

The numbers

Tekton Plumbing Roadmap

How Tekton builds, tests, and releases itself — and where we're heading.

This roadmap covers the infrastructure, CI/CD, and tooling that supports the tektoncd project. It is organized by workstream and prioritized using NOW / NEXT / SOON / LATER buckets.

Bucket	Meaning

@/tmp/test-alignment-report-v2.md

Diátaxis audit of Tekton Pipelines documentation

Diátaxis Audit of Tekton Pipelines Documentation

Audit of all 64 markdown files in docs/ against the Diátaxis documentation framework. Each document is classified by its primary type and whether it mixes types (hybrid).

Classification Key

Tekton Maintainer Triage Report

Date: March 6, 2026 Period analyzed: March 2025 – March 2026 (last 12 months) Data sources: GitHub API (PRs authored, PR reviews, issue comments, commits), Tekton DevStats (contributions, reviews, PRs, comments, commits), OWNERS files, org.yaml

Methodology

Per the Tekton Contributor Ladder:

Inactivity threshold: >4 months of no contributions, or >2 months of no communication

How did you get involved with Open Source?

I've always wanted to do Open Source, since I discovered it around 1999. The first Linux distribution I used was Red Hat Linux, and that was also my first encounter with Linux and Open Source. Little did I know that 20 years later I would work for the company that kind of introduced me to it!

I initially started looking into small projects I would need in my first startup job, like fog/fog, but what really got me started was the Docker project. Docker organized those "contribute meetups" in different places around their "birthday" and so, I made my first pull-request to the project that way. And from that point on, I was hooked. I also got involved a bit in the Archlinux User Repository when I was using it and now in NixOS.

What’s Open Source to you?

For me, Open Source is "the way" to do things. I truly believe into sharing commons and the fact that we do better when we work together, in the open. And Open Source embodies that.

	#!/usr/bin/env -S uv run --script
	# /// script
	# requires-python = ">=3.11"
	# dependencies = ["pyyaml"]
	# ///
	"""Tekton Catalog health analyzer.

	Walks the primary manifests in task/, pipeline/, and stepaction/ and produces
	a structured health report across several dimensions:

	#!/bin/bash

	set --noprofile --norc -e -o pipefail

	# Test script to validate the detect logic from ci.yaml

	echo "Testing detect logic for non-docs and yaml outputs"
	echo "==================================================="
	echo ""