-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/retest
triggered jobs on a PR that had needs-ok-to-test
label
#31763
Comments
/sig testing |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
What happened:
k8s-ci-robot
added theneeds-ok-to-test
label on the PR./retest
comment was given.main
branch also started. (These were the first runs of the prow jobs, not a restart as can be seen from here)What you expected to happen:
needs-ok-to-test
label.How to reproduce it (as minimally and precisely as possible):
org/repo
by auser
, whereuser
is not a member of theorg
. Theorg/repo
also should havetrigger_github_workflows
set totrue
in the prowtrigger
plugin config.repo
should have both github actions and prow jobs configured.needs-ok-to-test
label is presentretest
. This will restart the failed github action job. Also the prow jobs will be started (NOTE: not restarted, it will be freshly triggered.)Please provide links to example occurrences, if any:
Anything else we need to know?:
The
user
who commented/retest
had write access to the repository.The text was updated successfully, but these errors were encountered: