Repository navigation
ROSAENG-64870 Pin fullsend dispatch to post-v0.43.0 for OWNERS authorization - #971
Conversation
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>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughFullsend configuration adds the ChangesFullsend authorization
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to 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)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@RaphaelBut: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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