Repository navigation
HYPERFLEET-1762 - chore: narrow OWNERS to area owners and aliases - #1
Merged
ciaranRoche merged 1 commit intoOct 13, 2026
Conversation
This was referenced Oct 12, 2026
HYPERFLEET-1762 - ci: squash on merge for openshift-hyperfleet, hooks v0.3.0
openshift/release#86873
Merged
Merged
ciaranRoche
changed the title
ciaranRoche
force-pushed
the
HYPERFLEET-1200-owners-files
branch
from
October 12, 2026 11:45
effaa64 to
f193429
Compare
ciaranRoche
force-pushed
the
HYPERFLEET-1200-owners-files
branch
from
October 13, 2026 09:41
f193429 to
c51e825
Compare
ciaranRoche
marked this pull request as ready for review
October 13, 2026 14:10
Member
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rafabene The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-merge-bot Bot
added a commit
to openshift-hyperfleet/hyperfleet-adapter
that referenced
this pull request
Oct 13, 2026
## 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. openshift-hyperfleet/architecture#232, ownership document and generator. 2. openshift-hyperfleet/hyperfleet-hooks#17, commitlint validates the PR title only, then the `v0.3.0` tag. 3. 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: - openshift-hyperfleet/architecture#233 - openshift-hyperfleet/coderabbit#5 - **#331 (this PR)** - openshift-hyperfleet/hyperfleet-api#398 - openshift-hyperfleet/hyperfleet-api-spec#68 - openshift-hyperfleet/hyperfleet-api-spec-template#14 - openshift-hyperfleet/hyperfleet-applier#58 - openshift-hyperfleet/hyperfleet-broker#29 - openshift-hyperfleet/hyperfleet-claude-plugins#100 - openshift-hyperfleet/hyperfleet-credential-provider#15 - openshift-hyperfleet/hyperfleet-e2e#164 - openshift-hyperfleet/hyperfleet-hooks#18 - openshift-hyperfleet/hyperfleet-infra#108 - openshift-hyperfleet/hyperfleet-logger#6 - openshift-hyperfleet/hyperfleet-operator#129 - openshift-hyperfleet/hyperfleet-release#13 - openshift-hyperfleet/renovate-config#5 - openshift-hyperfleet/hyperfleet-sentinel#280 - openshift-hyperfleet/.github#1 6. openshift/release#86873, squash on merge and the commitlint pin bump, after 2. 7. openshift-hyperfleet/hyperfleet-claude-plugins#101, open-PRs digest by area, any time after 5. /hold
openshift-merge-bot Bot
pushed a commit
to openshift-hyperfleet/hyperfleet-claude-plugins
that referenced
this pull request
Oct 14, 2026
…quested reviewers (#101) ## What changed - The open-PRs digest groups PRs by their `area/*` label (first area as the group, others inline, "No area" last) and shows, per PR, the requested reviewers and business days since the request. A pending request older than one business day on a non-draft PR is flagged. Risk scoring, tiers and the Slack message shape are unchanged. - `collect-data.sh` reads `review_requested` events from the issue timeline so the request time is real, with PR `createdAt` as the fallback. - `prioritization-algorithm.md` and `output-format.md` replace "review requests are ignored because reviewers are auto-assigned" with the new rule: requests come from the area's OWNERS pool and are the reviewer of record. - `references/github-repos.md` is the current nineteen repositories (archived and out-of-scope ones removed, `hyperfleet-api-spec-template` added). - `bugs-triage/references/owners.csv` aligned with the ownership areas. - `CONTRIBUTING.md` and `AGENTS.md`: plugin OWNERS files reference aliases from the root `OWNERS_ALIASES` and are generated from the ownership document in the architecture repository. - `hyperfleet-work-triage` bumped to 0.4.0. ## Why Prow now labels PRs by area and requests reviewers from the area's OWNERS pool. The digest is what tells an approver every morning that a PR is waiting on them, so it has to show the area and the reviewer of record rather than ignoring requests. ## How to test ```text bash hyperfleet-work-triage/skills/open-prs/scripts/tests/run-tests.sh ``` 96 tests pass. A live run of `collect-data.sh --repo hyperfleet-adapter` returned real request timestamps from the timeline for adapter#330. Tracked in https://redhat.atlassian.net/browse/HYPERFLEET-1762 ## Merge order This is step 7 of the HyperFleet repository ownership rollout. It can merge any time after the area labels exist (they do), and is most useful once the OWNERS PRs (step 5) have merged. 1. openshift-hyperfleet/architecture#232, ownership document and generator. 2. openshift-hyperfleet/hyperfleet-hooks#17, commitlint validates the PR title only, then the `v0.3.0` tag. 3. 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. The nineteen per-repository OWNERS PRs, after 1 and 3, when the hold is lifted: - openshift-hyperfleet/architecture#233 - openshift-hyperfleet/coderabbit#5 - openshift-hyperfleet/hyperfleet-adapter#331 - openshift-hyperfleet/hyperfleet-api#398 - openshift-hyperfleet/hyperfleet-api-spec#68 - openshift-hyperfleet/hyperfleet-api-spec-template#14 - openshift-hyperfleet/hyperfleet-applier#58 - openshift-hyperfleet/hyperfleet-broker#29 - #100 - openshift-hyperfleet/hyperfleet-credential-provider#15 - openshift-hyperfleet/hyperfleet-e2e#164 - openshift-hyperfleet/hyperfleet-hooks#18 - openshift-hyperfleet/hyperfleet-infra#108 - openshift-hyperfleet/hyperfleet-logger#6 - openshift-hyperfleet/hyperfleet-operator#129 - openshift-hyperfleet/hyperfleet-release#13 - openshift-hyperfleet/renovate-config#5 - openshift-hyperfleet/hyperfleet-sentinel#280 - openshift-hyperfleet/.github#1 6. openshift/release#86873, squash on merge and the commitlint pin bump, after 2. 7. **This PR.** #101, open-PRs digest by area, any time after 5. --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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).
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.
v0.3.0tag.tidecontext. Independent of 1 and 2./hold