-
Notifications
You must be signed in to change notification settings - Fork 60
Pull requests: openshift/sippy
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
Automated - Update config ./config/openshift.yaml
#2143
opened Nov 27, 2024 by
openshift-bot
Loading…
TRT-1864: enable 4.19 views
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.
#2139
opened Nov 25, 2024 by
neisw
Loading…
TRT-1338: Potential replacement for the remaining 35 minute matview: Test analysis by job
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.
#2074
opened Oct 31, 2024 by
dgoodwin
Loading…
NO-JIRA: debug jiraloader component
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.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#2067
opened Oct 28, 2024 by
neisw
Loading…
Implement Jira integration with component readiness regressions
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.
#2041
opened Oct 7, 2024 by
xueqzhan
Loading…
Automated - Update never-stable
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
#2004
opened Sep 24, 2024 by
openshift-trt
Loading…
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.
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.
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.
ProTip!
no:milestone will show everything without a milestone.