-
Notifications
You must be signed in to change notification settings - Fork 55
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
Move Snyk Scripts from k/test-infra to k/sig-security/sig-security-tooling #60
Comments
@PushkarJ: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold for kubernetes/test-infra#27309 |
Hi @PushkarJ is this issue open for contribution? |
Yes the PR blocking it is merged. So you can work on this if you'd like |
/assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
As we learnt from kubernetes/test-infra#26896 (comment) it is possible for prow to pick up shell scripts outside of
k/test-infra
.Moving the script that is present here: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-k8s-infra/trusted/sig-security-trusted.yaml#L29-L87 into a dedicated shell script with name
build-deps-and-release-images.sh
underk/sig-security/sig-security-tooling/scanning
would be great for faster iteration and approvals and reviews can be managed within SIG Security members./sig security
/good-first-issue
/help
The text was updated successfully, but these errors were encountered: