Repository navigation
Add contribution 101 #266
Description
Activity
Perhaps also some guidelines on how and when one should write different types of tests (unit, integration, e2e...)?
That is a good idea. I can start something and then we can all contribute to it.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with/remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale- addedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
on Jul 14, 2019 /remove-lifecycle stale
- removedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
on Jul 26, 2019 /assign
- addedkind/documentationCategorizes issue or PR as related to documentation.Categorizes issue or PR as related to documentation.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
on Sep 11, 2019 What is generated, semi-generated, and manual
What is base repo and how it is related to this repoThe original design was https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/csi-new-client-library-procedure.md
Also it would be great if we have document around how to run tests in this repo. Ref: kubernetes-client/python-base#126 (comment)
/assign
Thanks for the ping - it will be done - I just returned from a conference and regained my desktop.
Add a contribution document explain the structure of the repo and best practices to start developing. Topics includes (but not limited to):