Skip to content

ROSAENG-64870 Pin fullsend dispatch to post-v0.43.0 for OWNERS authorization - #971

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
RaphaelBut:fullsend-owners-auth
Sep 23, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
RaphaelBut:fullsend-owners-auth

Conversation

@RaphaelBut

@RaphaelBut RaphaelBut commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

trying out prow/owners authorization for fullsend

Pin reusable-dispatch.yml to 5c8aefaf (fullsend-ai/fullsend#6051) to pick up opt-in Prow OWNERS file authorization for slash commands ahead of the next fullsend release. Enable the feature by adding the owners_file authorization provider to .fullsend/config.yaml.

Only the native dispatch workflow is updated; the Jira poll workflow stays on v0.43.0 since it does not need OWNERS auth.

This is a temporary pin — the next fullsend version bump should replace the SHA with the release tag.

Summary by CodeRabbit

  • New Features
    • Dispatch workflows now use the configured owners file for authorization, so access is determined by the repository’s ownership rules. This provides a consistent way to control who can run dispatches.

Pin reusable-dispatch.yml to 5c8aefaf (fullsend-ai/fullsend#6051) to
pick up opt-in Prow OWNERS file authorization for slash commands ahead
of the next fullsend release. Enable the feature by adding the
owners_file authorization provider to .fullsend/config.yaml.

Only the native dispatch workflow is updated; the Jira poll workflow
stays on v0.43.0 since it does not need OWNERS auth.

This is a temporary pin — the next fullsend version bump should replace
the SHA with the release tag.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 23, 2026 •

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 0398892f-f5fb-4b3e-96e1-1432732a30e4

📥 Commits

Reviewing files that changed from the base of the PR and between b7f0c6f and b331313.

📒 Files selected for processing (2)
  • .fullsend/config.yaml
  • .github/workflows/fullsend.yaml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Walkthrough

Fullsend configuration adds the owners_file authorization provider. The dispatch job now references an updated reusable workflow revision.

Changes

Fullsend authorization

Layer / File(s) Summary
Configure authorization and dispatch
.fullsend/config.yaml, .github/workflows/fullsend.yaml
The Fullsend configuration adds the owners_file authorization provider. The dispatch job updates its reusable workflow reference.

Priority: ⬇️ Low

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

Change: Feature

Suggested reviewers: samanthajayasinghe

Merge Risk: ⚪ Minimal · up to b3313

OWNERS authorization is enabled for slash commands, with the workflow’s documented collaborator-permission fallback. Unauthorized commands do not dispatch; no actionable merge risk remains.

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the main change: pinning the fullsend dispatch workflow to enable OWNERS authorization. It is specific, concise, and aligned with the pull request objectives.
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. The diff adds authorization configuration and changes a reusable workflow SHA. It adds or changes no Ginkgo…
Test Structure And Quality ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. It adds authorization configuration and updates a reusable workflow pin. It adds or modifies no Ginkgo test…
Microshift Test Compatibility ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. The diff adds authorization configuration and changes a reusable workflow pin. It adds no Ginkgo tests or t…
Single Node Openshift (Sno) Test Compatibility ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. The diff adds an authorization provider and changes a reusable workflow pin. It adds no Ginkgo e2e tests, s…
Topology-Aware Scheduling Compatibility ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. It adds a Fullsend authorization provider and changes a reusable GitHub Actions workflow reference. It does…
Ote Binary Stdout Contract ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. It adds an authorization provider and updates an external reusable workflow SHA. It does not change OTE bin…
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The pull request changes only .fullsend/config.yaml and .github/workflows/fullsend.yaml. The diff adds an authorization provider and changes a reusable workflow pin. It adds no Ginkgo tests or oth…
No-Weak-Crypto ✅ Passed The pull request changes only Fullsend authorization configuration and a reusable workflow commit pin. The diff introduces no MD5, SHA1, DES, 3DES, RC4, Blowfish, ECB mode, custom cryptography, or sec…
Container-Privileges ✅ Passed The pull request changes only .fullsend/config.yaml and the GitHub Actions workflow. The additions are the owners_file authorization provider and a reusable workflow SHA. No container or Kubernete…
No-Sensitive-Data-In-Logs ✅ Passed The PR adds only the owners_file authorization provider and changes the reusable workflow SHA. The added lines contain no logging commands or sensitive-data output. Existing secret references and no…
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 23, 2026
@openshift-ci

openshift-ci Bot commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

@RaphaelBut: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bergmannf

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 23, 2026
@openshift-ci

openshift-ci Bot commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bergmannf, RaphaelBut

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 [RaphaelBut,bergmannf]

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

@openshift-merge-bot
openshift-merge-bot Bot merged commit eee6ca8 into openshift:master Sep 23, 2026
38 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants