Skip to content

Adds documentation to support agentic workflows#20665

Open
jkhelil wants to merge 1 commit into
nextfrom
add_agent_context
Open

Adds documentation to support agentic workflows#20665
jkhelil wants to merge 1 commit into
nextfrom
add_agent_context

Conversation

@jkhelil

@jkhelil jkhelil commented May 4, 2026

Copy link
Copy Markdown

No description provided.

@openshift-ci openshift-ci Bot requested review from ppitonak and savitaashture May 4, 2026 16:55
@openshift-ci

openshift-ci Bot commented May 4, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jkhelil
Once this PR has been reviewed and has the lgtm label, please assign ppitonak for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jkhelil jkhelil changed the title Adds tooling and documentation to support agentic workflows Adds documentation to support agentic workflows May 4, 2026

@aThorp96 aThorp96 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also include a note about the branching strategy. The main branch is still the default branch and where all the Github Action automation lives, but next is used in some cases alongside release-vX.Y.x

Comment thread AGENTS.md

It vendors [`tektoncd/operator`](https://github.com/tektoncd/operator) and assembles OpenShift-specific customizations, image references, and OLM (Operator Lifecycle Manager) artifacts needed to ship OpenShift Pipelines as a supported Red Hat product.

## What This Repo Does

@aThorp96 aThorp96 May 7, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the OLM bundle and Operator component are only tangentially related, this clarifies that there's two (and sometimes three) artifacts

Suggested change
## What This Repo Does
## What This Repo Does
This repo serves two purposes. It vendors the upstream `tektoncd/operator` to build the downstream Operator (the component) and also builds the OLM Bundle which installs the Operator. These are two related but distinct responsibilities.
In order to serve these two purposes, this repo does the following:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants