-
Notifications
You must be signed in to change notification settings - Fork 61
Pull requests: openshift/sippy
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
Automated - Update never-stable
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
#2191
opened Dec 19, 2024 by
openshift-trt
Loading…
TRT-1107: move neverstable cron script here for GH app auth
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.
#2188
opened Dec 18, 2024 by
sosiouxme
Loading…
TRT-1912: Treat flake as failures in component readiness
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.
#2172
opened Dec 12, 2024 by
xueqzhan
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…
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.
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.
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/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
ProTip!
no:milestone will show everything without a milestone.