You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+22-4Lines changed: 22 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -20,13 +20,21 @@ The repository of the Kubernetes Python client consists of this main repository
20
20
### Where to Submit Your Patch
21
21
22
22
These folders are automatically generated. You will need to submit a patch to the upstream kubernetes repo [kubernetes](https://github.com/kubernetes/kubernetes) or the OpenAPI generator repo [openapi-generator](https://github.com/OpenAPITools/openapi-generator). This contains:
The base repo contains developer written codes only. The patches should be sent to the base repo instead. The scope covers these repos and symbolic links in the main repo:
@@ -52,7 +60,7 @@ The symbolic links contained in this repo does not work for Windows operating sy
52
60
53
61
### Writing Tests
54
62
55
-
In addition to running the your fix yourself and tell us that your fix works, you can demonstrate that your fix really works by using unit tests. These unit tests are mainly located in three places. You should put your tests into the places that they fit in.
63
+
In addition to running the your fix yourself and tell us that your fix works, you can demonstrate that your fix really works by using unit tests and end to end tests. These unit tests are mainly located in three places. You should put your tests into the places that they fit in.
56
64
57
65
1.[Generated tests](kubernetes/test) by OpenAPI generator: these tests should pass and do not require modification.
58
66
2.[End to end tests](kubernetes/e2e_test): these are tests that can only be verified with a live kubernetes server.
@@ -72,3 +80,13 @@ If you write a new end to end (e2e) test, or change behaviors that affect e2e te
72
80
73
81
3. Check the test results and make corresponding fixes.
74
82
83
+
## Update the Base Submodule in the Main Repo After Your python-base PR Is Merged
84
+
85
+
Your contribution of the base repo will not be automatically reflected in the main repo after your PR is merged. Instead, please update the ```base``` submodule in your fork of the main repo as follows:
86
+
```bash
87
+
$ cd kubernetes/base
88
+
$ git fetch origin
89
+
$ git checkout origin/master # assuming your change has been merged into the latest python-base MASTER
90
+
$ cd ../..
91
+
```
92
+
You may now add a release note to [CHANGELOG.md](CHANGELOG.md) if needed and then commit and push to your fork. You can now send a PR to this main repo to complete your contribution.
0 commit comments