History

Kubernetes Submit Queue a1e786f138 Merge pull request #54059 from porridge/fix-lint-err Automatic merge from submit-queue (batch tested with PRs 53696, 54059). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Fix lint warnings for useless err checks. What this PR does / why we need it: This check was recently added to golint. Which issue this PR fixes Related to #37254 Release note: ```release-note NONE ```		2017-10-18 00:58:59 -07:00
..
src/k8s.io	Merge pull request #54059 from porridge/fix-lint-err	2017-10-18 00:58:59 -07:00
BUILD	Merge pull request #49654 from jcbsmpsn/move-certificate-manager	2017-10-06 15:00:07 -07:00
OWNERS	…
README.md	staging README: update code-generator to published	2017-10-17 20:54:35 +05:30

README.md

External Repository Staging Area

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.

Repositories currently staged here:

The code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code.

Using staged repositories from Kubernetes code

Kubernetes code uses the repositories in this directory via symlinks in the vendor/k8s.io directory into this staging area. For example, when Kubernetes code imports a package from the k8s.io/client-go repository, that import is resolved to staging/src/k8s.io/client-go relative to the project root:

// pkg/example/some_code.go
package example

import (
  "k8s.io/client-go/dynamic" // resolves to staging/src/k8s.io/client-go/dynamic
)

Once the change-over to external repositories is complete, these repositories will actually be vendored from k8s.io/<package-name>.