[ciaranRoche]

What changed

Replaces the flat list of approvers and reviewers with area owners from the
ownership document: https://github.com/openshift-hyperfleet/architecture/blob/main/hyperfleet/docs/owners.md
(in review in openshift-hyperfleet/architecture#232 until it merges).

• OWNERS_ALIASES holds the names, OWNERS files reference aliases and carry area labels
• a merge now needs an approver for every touched path
• Blunderbuss requests reviewers from the area's pool

Why

Today every repository lists the same seventeen people as approvers and
reviewers, so review requests route at random and any one of them can merge
anything alone. Named areas put the request in front of the people who know the
code and make an approver accountable for what merges.

The same criteria were applied to everyone at launch, using the last three
sprints. Reviewer and approver status follows the criteria in the ownership
document and nothing else. The path to reviewer and approver is written there.

Generated from hyperfleet/docs/owners.yaml in the architecture repository.
Changes to ownership are a PR to that file, then a regenerated OWNERS here.

Tracked in https://redhat.atlassian.net/browse/HYPERFLEET-1762

Merge order

This is one of the nineteen per-repository OWNERS PRs, step 5 of the
repository ownership rollout. It merges after the ownership document and the Prow onboarding PR, and only
when the hold is lifted. The team session that announces the model has already
happened.

1. HYPERFLEET-1762 - docs: repository ownership document, OWNERS generator and review rules architecture#232, ownership document and generator.
2. HYPERFLEET-1762 - feat: validate the PR title only in --pr mode hyperfleet-hooks#17, commitlint validates the PR title only, then the v0.3.0 tag.
3. openshift-hyperfleet: onboard five repositories to Prow and require the tide context on repositories without jobs openshift/release#86872, Prow onboarding and the tide context. Independent of 1 and 2.
4. Team session. Done, held with the team the week of 5 October.
5. This PR. The nineteen per-repository OWNERS PRs, after 1 and 3, when the hold is lifted:
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases architecture#233
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases coderabbit#5
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-adapter#331
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-api#398
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases #68 (this PR)
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-api-spec-template#14
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-applier#58
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-broker#29
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-claude-plugins#100
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-credential-provider#15
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-e2e#164
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-hooks#18
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-infra#108
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-logger#6
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-operator#129
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-release#13
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases renovate-config#5
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases hyperfleet-sentinel#280
   • HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases .github#1
6. HYPERFLEET-1762 - ci: squash on merge for openshift-hyperfleet, hooks v0.3.0 openshift/release#86873, squash on merge and the commitlint pin bump, after 2.
7. HYPERFLEET-1762 - feat: group the open PRs digest by area and show requested reviewers hyperfleet-claude-plugins#101, open-PRs digest by area, any time after 5.

/hold

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Central YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Enterprise
• Run ID: f491d8ad-7ce9-4280-862c-b71bab014de9

📥 Commits

Reviewing files that changed from the base of the PR and between 42a7434 and b6be234.

📒 Files selected for processing (2)

• OWNERS
• OWNERS_ALIASES

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• openshift-hyperfleet/architecture (manual) → reviewed against open PR #232 HYPERFLEET-1200-owners-areas instead of the default branch
• openshift-hyperfleet/hyperfleet-api (manual) → reviewed against open PR #398 HYPERFLEET-1200-owners-files instead of the default branch
• openshift-hyperfleet/hyperfleet-sentinel (manual) → reviewed against open PR #280 HYPERFLEET-1200-owners-files instead of the default branch
• openshift-hyperfleet/hyperfleet-adapter (manual) → reviewed against open PR #331 HYPERFLEET-1200-owners-files instead of the default branch
• openshift-hyperfleet/hyperfleet-broker (manual) → reviewed against open PR #29 HYPERFLEET-1200-owners-files instead of the default branch

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 9 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Contract-related changes are now routed to designated owner and reviewer teams instead of being assigned through individual approver and reviewer lists.
  • Contract ownership and review responsibilities are mapped to their respective team members, and a contract-area label is applied.

The change adds aliases for the contracts-owners and contracts-reviewers teams. It replaces individual approvers and reviewers in OWNERS with those teams and adds the area/contracts label.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to b6be2

The ownership configuration follows the documented alias and approver/reviewer conventions, with no identified code-level blocker to merging.

Pre-merge checks · 11

Passed checks (11 passed)

Check name	Status	Explanation
Title check		The title clearly identifies the ownership-scope change and the addition of aliases.
Description check		The description directly explains the OWNERS and OWNERS_ALIASES changes, their purpose, rollout order, and merge conditions.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Sec-02: Secrets In Log Output		The pull request changes only OWNERS and adds OWNERS_ALIASES. The diff contains no Go or other source files and no slog, log, logr, zap, or fmt.Print* statements. SEC-02 is not triggered…
No Hardcoded Secrets		PASS. The pull request changes only OWNERS and adds OWNERS_ALIASES. The added values are team aliases and usernames. No API keys, tokens, passwords, private keys, embedded URL credentials, base64 …
No Weak Cryptography		PASS — The pull request changes only OWNERS and adds OWNERS_ALIASES. The diff contains no cryptographic code, cryptographic primitives, secret comparisons, or custom cryptographic implementation. …
No Injection Vectors		PASS — The pull request changes only OWNERS and adds OWNERS_ALIASES. The diff contains no SQL queries, fmt.Sprintf, exec.Command/exec.CommandContext, template.HTML, or YAML unmarshalling. …
No Privileged Containers		PASS: The pull request changes only OWNERS and OWNERS_ALIASES. These files are not Kubernetes/OpenShift manifests, Helm templates, or Dockerfiles. The patch adds no privileged-container setting or…
No Pii Or Sensitive Data In Logs		PASS: The pull request changes only OWNERS and adds OWNERS_ALIASES. The diff contains no logging statements or runtime code, so it cannot introduce PII, session IDs, raw request or response body l…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

✨ Simplify code

• Create a new PR

_{Comment @coderabbitai help to get the list of available commands.}

[ciaranRoche]

/unhold

[rafabene]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rafabene

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rafabene]

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