Skip to content

Pull requests: openshift/client-go

New pull request New
7 Open 296 Closed
7 Open 296 Closed
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
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

[WIP] just for Pr 349 buid do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#356 opened Dec 24, 2025 by zhaozhanqi • Draft
1
NO-JIRA: bump openshift/api 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#354 opened Dec 15, 2025 by sanchezl Loading…
7
[WIP] Regenerate apply configurations for OVN no-overlay mode do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#349 opened Dec 1, 2025 by ricky-rav Loading…
2
WIP: Rebase 1.35 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#346 opened Nov 19, 2025 by jacobsee Loading…
2
WIP do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#345 opened Nov 14, 2025 by QiWang19 • Draft
5
NO-JIRA: Bump openshift/api dependency jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#344 opened Nov 11, 2025 by perdasilva Loading…
3
[release-4.18]: regenerates client-go for OCL 4.18 backport 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. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#335 opened Aug 15, 2025 by cheesesashimi Loading…
@JoelSpeed @zhouying7780
@xingxingxia @wangke19 @gangwgr
5
ProTip! Filter pull requests by the default branch with base:master.