e123311d8a
Automatic merge from submit-queue Fix link to apiextensions client-go example Fixes link to client-go example for apiextensions-apiserver. Fixing #47211. **Special notes for your reviewer**: When I run `hack/update-staging-client-go.sh`, I get this error: ``` !!! Error in staging/copy.sh:132 Error in staging/copy.sh:132. 'git commit -q -m "Snapshot" > /dev/null' exited with status 1 Call stack: 1: staging/copy.sh:132 main(...) Exiting with status 1 ``` What am I missing here? /cc @caesarxuchao @sttts **Release note**: ``` NONE ``` |
||
|---|---|---|
| .. | ||
| src/k8s.io | ||
| OWNERS | ||
| README.md | ||
| copy.sh | ||
| godeps-json-updater.go | ||
| prime-apimachinery.sh | ||
README.md
This directory is the staging area for packages that have been split to their own repository. The content here will be periodically published to respective top-level k8s.io repositories.
Most code in the staging/ directory is authoritative, i.e. the only copy of
the code. You can directly modify such code. However the packages in
staging/src/k8s.io/client-go/pkg are copied from pkg/. If you modify the
original code in pkg/, you need to run hack/godep-restore.sh from the k8s
root directory, followed by hack/update-staging-client-go.sh. We are working
towards making all code in staging/ authoritative.
The vendor/k8s.io directory contains symlinks pointing to this staging area,
so to use a package in the staging area, you can import it as
k8s.io/<package-name>, as if the package were vendored. Packages will be
vendored from k8s.io/<package-name> for real after the test matrix is
converted to vendor k8s components.