Skip to content

Pull requests: openshift/operator-framework-operator-controller

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort

Pull requests list

[release-4.19] OCPBUGS-56634: set SELinux type for operator-controller approved Indicates a PR has been approved by an approver from all required OWNERS files. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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. qe-approved Signifies that QE has signed off on this PR
#360 opened May 23, 2025 by openshift-cherrypick-robot Loading…
OCPBUGS-56569: [release-4.18] fix: don't template registry+v1 manifests approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
#354 opened May 21, 2025 by joelanford Loading…
OPRUN-3913: [release 4.18] [Default Catalog Tests] - Cherry pick to 4.18 - Initial implementation do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#349 opened May 19, 2025 by camilamacedo86 Loading…
OCPBUGS-56045: Bump catalog versions to 4.19 [release-4.19] approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-bug Indicates that a referenced Jira bug is valid 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. qe-approved Signifies that QE has signed off on this PR
#335 opened May 12, 2025 by tmshort Loading…
OPRUN-3809: [release-4.17] - Intial implementation for Catalog tests do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#332 opened May 2, 2025 by camilamacedo86 Loading…
ProTip! Filter pull requests by the default branch with base:main.