Draft
Conversation
Contributor
Author
|
This change is part of the following stack: Change managed by git-spice. |
|
Skipping CI for Draft Pull Request. |
Contributor
There was a problem hiding this comment.
The pull request #17809 has too many files changed.
The GitHub API will only let us fetch up to 300 changed files, and this pull request has 652.
9 tasks
2858333 to
f2eec35
Compare
This was referenced Nov 24, 2025
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #17809 +/- ##
=======================================
Coverage 49.52% 49.52%
=======================================
Files 2666 2666
Lines 201181 201181
=======================================
+ Hits 99629 99632 +3
+ Misses 94115 94113 -2
+ Partials 7437 7436 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This was referenced Nov 25, 2025
65303ba to
69d9c49
Compare
674d509 to
31f3270
Compare
9b3f0c0 to
39cdb0e
Compare
39cdb0e to
63e3116
Compare
This was referenced Jan 30, 2026
c312405 to
731e227
Compare
This was referenced Feb 3, 2026
661fb1f to
eb11e65
Compare
Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
3ff1bfd to
de1e05a
Compare
9 tasks
This was referenced Feb 25, 2026
Signed-off-by: Saif Chaudhry <schaudhr@redhat.com>
This was referenced Feb 26, 2026
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update UI to PatternFly 6.
The core of this PR is an update to all PatternFly and Victory dependencies, followed by running PatternFly's automated CODEMOD tools. Few or zero manual changes have been made in this branch.
The plan
In order to make this upgrade as reviewable and pain-free as possible, the change will be broken down into many separate reviewable pull requests.
Once all individual PRs are reviewed and approved, we will bug bash the changes as a whole and squash down into a single PR (this one!) so that the entirety of the change lands onUpdate as of Dec 1 after UI team sync: we are going to merge the branched PRs into this base PR as they are approved in order to reduce the burden of review (and CI) having many tens of changes open at once. The approvals for all of the individual PRs in combination with team testing of the change as a whole should serve as approval enough for this PR without having to re-read the changes again in aggregate.masterat once. This is necessary due to the nature of the change, which otherwise would introduce many UI bugs.I @dvail intend on using
git-spiceto stack all changes I make in a linear sequence of PRs. See #17809 (comment). Any other contributors can feel free to branch off where you feel it makes sense, but the further up the stack the better. I will rebase all of my changes frequently to avoid merge conflicts that spiral out of control and make it clear in the channel so that contributors can rebase their branches against the updated targets.Contents
To see existing problems, markup structure changes, etc: (note that you will want to clear out
./buildto prevent false positives)Changes applied in this PR:
User-facing documentation
Testing and quality
Automated testing
How I validated my change
I validated that this change breaks every page in the application. Do not merge yet.