when I read this document automation.md:
Before a PR from an unknown user is run, the PR builder bot (
@k8s-ci-robot) asks to a message from a kubernetes member that a PR is safe to test, the member can reply with the
/ok-to-testcommand on a single line to begin CI testing.
Any pushes of new code to the PR will automatically trigger a new test
I have several questions:
k8s member refers to the who?
k8s member = reviewers? or k8s member = reviewers + approvers?
Any pushes of new code to the PR will automatically trigger a new test, is it mean after PR created the new content push to PR ? or from the initialization of PR?
I checked PRs of kubernetes in GitHub, I found most PRs do not have
/ok-to-testcommand under comments. whether mean not all of PRs are necessary to test?
Add e2e test helpers for DaemonSets by creydr · Pull Request #105486 · kubernetes/kubernetes · GitHub