In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

• Replace individual approvers/reviewers with the @konflux-infra GitHub team for infra-owned areas.
• Add missing component OWNERS files to establish clear review/approval ownership.
• Simplify root OWNERS to delegate approvals to the infra team alias.

graph TD
  PR["PR change"] --> OWN["OWNERS files"] --> PROW["OWNERS plugin"] --> TEAM["@konflux-infra"]
  OWN --> ROOT["repo root"]
  OWN --> CMPS["infra components"]
  subgraph Legend
    direction LR
    _doc["File/Config"] ~~~ _svc["Automation"] ~~~ _team["GitHub team"]
  end

Loading

The following are alternative approaches to this PR:

1. Add a single parent OWNERS under components/

• ➕ Reduces duplication across many component directories
• ➕ Makes future infra-owned additions inherit ownership automatically
• ➖ May be too broad if some components need different owners
• ➖ Harder to express exceptions without additional override OWNERS files

2. Keep per-component OWNERS but also add a brief ownership policy doc

• ➕ Maintains precise ownership boundaries per component
• ➕ Documents why/when @konflux-infra should be used
• ➖ Adds a documentation maintenance burden
• ➖ Doesn’t reduce ongoing OWNERS churn as much as inheritance

Recommendation: Current approach is good if ownership must be explicit per infra-owned component and if other components should not inherit infra ownership. If more infra-owned components are expected soon, consider adding a parent components/ OWNERS (with per-component overrides as needed) to reduce repetitive edits.

Other (8) +35 / -42

OWNERSReplace root approvers list with @konflux-infra +1/-6

Replace root approvers list with @konflux-infra

• Removes the explicit list of individual approvers and replaces it with the @konflux-infra team alias at the repository root. This centralizes top-level approval authority to the infra team.

OWNERS

OWNERSDelegate ArgoCD repo secrets ownership to @konflux-infra +2/-12

Delegate ArgoCD repo secrets ownership to @konflux-infra

• Replaces individual approvers and reviewers with the @konflux-infra team. This standardizes ownership for this infra-owned component.

components/argocd-repo-secrets/OWNERS

OWNERSAdd OWNERS for external-secrets-operator under infra ownership +7/-0

Add OWNERS for external-secrets-operator under infra ownership

• Introduces a new OWNERS file defining @konflux-infra as both approver and reviewer. Establishes explicit code ownership for the component.

components/external-secrets-operator/OWNERS

OWNERSDelegate IAM component ownership to @konflux-infra +2/-12

Delegate IAM component ownership to @konflux-infra

• Replaces the existing individual approvers and reviewers with the @konflux-infra team. Aligns IAM ownership with infra-owned conventions.

components/iam/OWNERS

OWNERSAdd OWNERS for kueue under infra ownership +7/-0

Add OWNERS for kueue under infra ownership

• Adds a new OWNERS file setting @konflux-infra as approvers and reviewers. Ensures review routing and approval requirements are owned by infra.

components/kueue/OWNERS

OWNERSAdd OWNERS for kyverno under infra ownership +7/-0

Add OWNERS for kyverno under infra ownership

• Adds a new OWNERS file designating @konflux-infra as approvers and reviewers. Makes ownership explicit for this infra-managed component.

components/kyverno/OWNERS

OWNERSAdd OWNERS for policies under infra ownership +7/-0

Add OWNERS for policies under infra ownership

• Adds a new OWNERS file that assigns approver/reviewer responsibility to @konflux-infra. Clarifies ownership for policy-related content.

components/policies/OWNERS

OWNERSDelegate rover-group-sync ownership to @konflux-infra +2/-12

Delegate rover-group-sync ownership to @konflux-infra

• Replaces the individual approver and reviewer lists with the @konflux-infra team. Standardizes ownership configuration for this component.

components/rover-group-sync/OWNERS

Description

The updated OWNERS files list approvers/reviewers as "@konflux-infra", but every other OWNERS file
in this repo uses raw GitHub logins without a leading "@", so this risks OWNERS-based ownership
matching not recognizing the intended owner.

Code

OWNERS[7]

+- @konflux-infra

Relevance

⭐⭐⭐ High

Repo OWNERS files use raw logins; prior OWNERS PRs show no '@'. PR #107 even had invalid-owners-file
enforcement.

PR-#107
PR-#271
PR-#118

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

All existing OWNERS files in this repo list approvers/reviewers as plain identifiers (no leading
@), while @ mention syntax appears in .github/CODEOWNERS. This PR introduces @konflux-infra
into OWNERS, making it inconsistent with established OWNERS formatting and likely to be
misinterpreted by OWNERS tooling expecting raw logins.

OWNERS[3-7]
components/argocd-repo-secrets/OWNERS[3-7]
components/internal-services/OWNERS[3-15]
.github/CODEOWNERS[1-15]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Several `OWNERS` files now use `@konflux-infra` as an approver/reviewer entry. In this repository, `OWNERS` files consistently list *raw* GitHub logins (no leading `@`), while `@user` mention syntax is used in `.github/CODEOWNERS`. Using `@...` in `OWNERS` risks the owner value being treated as a literal string that doesn't match the intended GitHub identity.

## Issue Context
This PR updates multiple OWNERS files to infra ownership and introduces `@konflux-infra` in both `approvers:` and `reviewers:`.

## Fix Focus Areas
- OWNERS[7-7]
- components/argocd-repo-secrets/OWNERS[3-7]
- components/iam/OWNERS[3-7]
- components/rover-group-sync/OWNERS[3-7]
- components/external-secrets-operator/OWNERS[1-7]
- components/kueue/OWNERS[1-7]
- components/kyverno/OWNERS[1-7]
- components/policies/OWNERS[1-7]

## Suggested change
- Replace `- @konflux-infra` with the repo’s standard OWNERS identifier format (e.g., `- konflux-infra` without `@`, or the correct `org/team` string if this is meant to be a GitHub team), consistently across all touched `OWNERS` files.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

• OWNERS [enkeefe00,filariow]

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