-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Inputs for CONTRIBUTING.md #2293
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
Comments
/area contributor-guide |
I guess @VineethReddy02 created this issue for #1832 but since the README already mentions the contributor guide, is it overkill to have a |
I think creating a link is the way to go, if we kept stuff in contributing.md then that'd be one more file we'd have to check when fixing something. |
@VineethReddy02 would you like to put a help wanted label on this and see if we can get a contributor to do what @castrojo is suggesting? Or do you have a different direction in mind? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
We have a CONTRIBUTING.md file which has links to the contributor guide and other useful resources. Closing. Please reopen if needed. |
@nikhita: Closing this issue. 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. |
Contributing page would be a great entry point for beginners in getting started with there respective interest groups.
These following are some of the basic elements of a contributing page, feel free to add more.
1)Filing a bug
2)Sending a fix
Or else we will at least have pointer to generalized contributing page
https://github.com/kubernetes/community/blob/master/contributors/guide/README.md
The text was updated successfully, but these errors were encountered: