staging/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 kubesphere.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.
KubeSphere code uses the repositories in this directory via symlinks in the
vendor/kubesphere.io directory into this staging area. For example, when
KubeSphere code imports a package from the kubesphere.io/client-go repository, that
import is resolved to staging/src/kubesphere.io/client-go relative to the project
root:
// pkg/example/some_code.go
package example
import (
"kubesphere.io/client-go/" // resolves to staging/src/kubesphere.io/client-go/dynamic
)
Once the change-over to external repositories is complete, these repositories
will actually be vendored from kubesphere.io/<package-name>.
kubesphere/kubesphere:Add a propose to sig-architecture in community. Waiting approval for creating the staging repository.
Once approval has been granted, create the new staging repository.
Add a symlink to the staging repo in vendor/kubesphere.io.
Add all mandatory template files to the staging repo such as README.md, LICENSE, OWNER,CONTRIBUTING.md.
Create an repository in the KubeSphere org. The published repository must have an initial empty commit.
Setup branch protection and enable access to the ks-publishing-bot bot.
Once the repository has been created in the KubeSphere org, update the publishing-bot to publish the staging repository by updating:
rules.yaml:
Make sure that the list of dependencies reflects the staging repos in the Godeps.json file.Add the repo to the list of staging repos in this README.md file.