Skip to content

Pull requests: openshift/os

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
Sort

Pull requests list

tree: delete base compose files, rework README 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.
#1811 opened May 1, 2025 by jlebon Draft
NO-JIRA: Bump fedora-coreos-config jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1810 opened May 1, 2025 by coreosbot-releng Loading…
[DNM] Revert "Unpin libreswan version"
#1807 opened Apr 23, 2025 by pperiyasamy Loading…
OKD-240: set CentOS Stream 10 as default base layer for OKD node image 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.
#1806 opened Apr 22, 2025 by jcapiitao Loading…
NO-JIRA: bump verison to 4.20 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.
#1804 opened Apr 17, 2025 by mike-nguyen Loading…
[release-4.19] NO-JIRA: gitmodules: track rhcos-4.19 branch 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.
#1803 opened Apr 17, 2025 by mike-nguyen Loading…
NO-JIRA: Add Johan-Liebert1 (Pragyan Poudyal) to owners 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. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1766 opened Mar 12, 2025 by Johan-Liebert1 Loading…
ProTip! no:milestone will show everything without a milestone.