-
Notifications
You must be signed in to change notification settings - Fork 26
Pull requests: openshift/lightspeed-console
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
Update Konflux references
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
lgtm
Indicates that a PR is ready to be merged.
#1583
opened Mar 3, 2026 by
red-hat-konflux
bot
Loading…
1 task
Switch code blocks to use PF Chatbot code blocks
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
#1581
opened Mar 3, 2026 by
kyoto
Loading…
olsToolUIs initial support
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
Tests: Add check to ensure page has loaded before continuing
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
#1561
opened Feb 27, 2026 by
kyoto
Loading…
Tests: Fix intercept order to ensure it's in place before the API call
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
#1527
opened Feb 23, 2026 by
kyoto
Loading…
[WIP] OLS-2608: Automatically convert PromQL code blocks to QueryBrowser graphs
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.
OLS-2568: Mcp app interactive views
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.
OLS-2568: Mcp tool metadata and UI
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.
[pattern-fly-5] Tests: Remove footer check and fix non-hypershift cluster testing
#1234
opened Dec 4, 2025 by
kyoto
Loading…
[WIP] auto-include some context about console "state"
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1124
opened Nov 5, 2025 by
thoraxe
Loading…
ProTip!
Filter pull requests by the default branch with base:main.