forked from kubernetes/kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 112
Pull requests: openshift/kubernetes
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
OCPBUGS-45273: OCPBUGS-45275: Properly annotate networking skips created during rebase
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
lgtm
Indicates that a PR is ready to be merged.
#2235
opened Mar 6, 2025 by
bertinatto
WIP: OCPBUGS-42087: Add metric for watch cache ready
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
vendor-update
Touching vendor dir or related files
#2234
opened Mar 5, 2025 by
bertinatto
•
Draft
OCPBUGS-42087: storage/cacher/ready: dynamically calculate the retryAfterSeconds
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
vendor-update
Touching vendor dir or related files
#2225
opened Feb 28, 2025 by
bertinatto
OCPBUGS-51151: Propagate error when creating CustomResourceStorage instead of panicking
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/severity-critical
Referenced Jira bug's severity is critical for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
vendor-update
Touching vendor dir or related files
#2216
opened Feb 24, 2025 by
bertinatto
DO NOT MERGE: ocp-next
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
backports/unvalidated-commits
Indicates that not all commits come to merged upstream PRs.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
vendor-update
Touching vendor dir or related files
#2156
opened Dec 6, 2024 by
bertinatto
•
Draft
DO NOT MERGE: ocp-next
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
backports/validated-commits
Indicates that all commits come to merged upstream PRs.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
vendor-update
Touching vendor dir or related files
#2148
opened Nov 28, 2024 by
bertinatto
•
Draft
ProTip!
Add no:assignee to see everything that’s not assigned.