Add H1Bot security key process to on/offboarding documentation

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

tabbysable commented 2 years ago

/triage approved /lifecycle frozen

k8s-ci-robot commented 2 years ago

@tabbysable: The label(s) triage/approved cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/committee-security-response/issues/144#issuecomment-1118851924): >/triage approved >/lifecycle frozen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

kubernetes / committee-security-response

Add H1Bot security key process to on/offboarding documentation #144