issue-3260: Clarify a few points on Development Documentation.#3261
Conversation
|
Welcome @jgao1025! |
|
Hi @jgao1025. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
/ok-to-test Thanks @jgao1025, this is great stuff. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jgao1025, youngnick The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Co-authored-by: Mattia Lavacca <[email protected]>
|
This is really great, thanks @jgao1025! /lgtm |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
As a new contributor, I reviewed the Dev Guide and would like to clarify a few points I encountered while following it. I've made some structural adjustments and added a few pieces of content. I know that this may have some personal opinions, so I'm open to any feedback or comments.
Which issue(s) this PR fixes:
Fixes #3260
Does this PR introduce a user-facing change?:
NONE
Dear reviewers,
You can check the latest changes at here.