Skip to content

Pull requests: openshift/sippy

New pull request New
12 Open 1,963 Closed
12 Open 1,963 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
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

TRT-1811: POC fallback queries approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1993 opened Sep 15, 2024 by neisw • Draft
3
Add regressions for 4.17 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#1991 opened Sep 12, 2024 by neisw • Draft
4
Add regression for metal dualstack do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#1989 opened Sep 11, 2024 by neisw • Draft
2
TRT-1784: Add CGroupMode and ContainerRuntime variants to CR approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1977 opened Sep 6, 2024 by xueqzhan Loading…
6
Automated - Update never-stable needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
#1953 opened Aug 29, 2024 by openshift-trt Loading…
2
UI update for variant cross-comparison 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.
#1948 opened Aug 28, 2024 by sosiouxme • Draft
3
TRT-1702: Risk Analysis: ensure Test ID is populated do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1852 opened Jul 11, 2024 by sosiouxme • Draft
10
TRT-1738: WIP: GROTESQUE HACK: compare ha vs single approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
#1848 opened Jul 10, 2024 by dgoodwin Loading…
4
Update tests to use 4.17 approved Indicates a PR has been approved by an approver from all required OWNERS files. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1770 opened Jun 11, 2024 by stbenjam Loading…
3
[WIP] Adding a CR question/answer for missing basis runs do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1660 opened May 3, 2024 by brenton Loading…
5
WIP: Dynamic variants in Component Readiness approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1628 opened Apr 22, 2024 by dgoodwin Loading…
6
TRT-1574: Server Side Views approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1614 opened Apr 17, 2024 by dgoodwin Loading…
7
ProTip! What’s not been updated in a month: updated:<2024-08-19.