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
Explain SIGs better, note on where to find technical support #1505
Conversation
Hi @guineveresaenger. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. 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. |
/sig contributor-experience |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: castrojo, guineveresaenger The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/test all [submit-queue is verifying that this PR is safe to merge] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice changes. The commit "clarifying SIG and asking questions", or the PR summary if the commits are squashed for merge, should have text indicating deletion of the contributors/devel/welcome-to-kubernetes-new-developer-guide.md file, with its content superseded now by by the new contrib guide. Somebody accustomed to that file might be confused where it went. Covering the info in that file's "The Release Process and Code Freeze" section is still a gap in the new document.
Automatic merge from submit-queue. |
This is in partial fulfillment of umbrella issue #1413.