Skip to content

Pull requests: openshift/microshift

New pull request New
15 Open 5,678 Closed
15 Open 5,678 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

USHIFT-6361: Update scenario names for bootc standard1 and standard2 for releases 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.
#6019 opened Jan 5, 2026 by kasturinarra Loading…
@agullon
7
USHIFT-6432: Move rhel96-bootc.image-bootc to base group2 to optimize cache build time 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. verified Signifies that the PR passed pre-merge verification criteria
#6018 opened Jan 5, 2026 by ggiguash Loading…
@agullon
8
NO-ISSUE: Common versions update release 4.22 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.
#6016 opened Jan 5, 2026 by kasturinarra Loading…
@agullon
9
[release-4.22] NO-ISSUE: Update common_versions.sh jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#6014 opened Jan 5, 2026 by microshift-rebase-script bot Loading…
6
NO-ISSUE: rebase-release-4.22-4.22.0-0.nightly-2026-01-01-225210_amd64-2026-01-01_arm64-2026-01-04 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
#6011 opened Jan 5, 2026 by microshift-rebase-script bot Loading…
4
USHIFT-6437: Add a delay when restarting MicroShift service 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. verified Signifies that the PR passed pre-merge verification criteria
#6006 opened Jan 2, 2026 by ggiguash Loading…
@agullon
19
USHIFT-6362: Add iso deployment for rpmostree release scenarios 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.
#5996 opened Dec 30, 2025 by kasturinarra Loading…
14
USHIFT-6360: Merge 4 release scenarios into two 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. verified Signifies that the PR passed pre-merge verification criteria
#5994 opened Dec 30, 2025 by kasturinarra Loading…
@agullon
13
USHIFT-6423: Add release info images into the mirrored registry 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.
#5973 opened Dec 23, 2025 by ggiguash • Draft
17
[release-4.21] USHIFT-6074: Add support on releases scenarios to use artifacts from konflux 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.
#5950 opened Dec 19, 2025 by agullon Loading…
17
USHIFT-6340: Update list of ginkgo tests after openshift-tests-private release-4.22 banch is unforzen 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. 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.
#5918 opened Dec 16, 2025 by agullon • Draft
7
USHIFT-6073: Add upgrade path on releases scenarios: from Z-1 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.
#5862 opened Dec 5, 2025 by agullon Loading…
21
USHIFT-6381: Add profile.robot Test Suite into bootc releases scenarios 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#5850 opened Dec 3, 2025 by agullon • Draft
33
OCPEDGE-2038: Add promote-learner command 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.
#5706 opened Nov 7, 2025 by pacevedom • Draft
3
USHIFT-6074: Add support on releases scenarios to use artifacts from konflux 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.
#5596 opened Oct 10, 2025 by agullon Loading…
42
ProTip! Follow long discussions with comments:>50.