Remove cluster-image-registry-operator's no-FF requirements - #82832
Remove cluster-image-registry-operator's no-FF requirements#82832patrickdillon wants to merge 1 commit into
Conversation
The docs-approved, px-approved label requirements are legacy. This process is no longer used.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
WalkthroughThe Prow Tide configuration removes obsolete excluded-branch and separate branch queries. The remaining Changes
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: patrickdillon 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 |
|
[REHEARSALNOTIFIER] Note: If this PR includes changes to step registry files ( |
|
@patrickdillon: 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. |
The docs-approved, px-approved label requirements are legacy. This process is no longer used.
Summary by CodeRabbit
cluster-image-registry-operatorProw configuration.docs-approvedandpx-approvedlabel requirements from Tide no-fast-forward checks.