Disable GitHub Issues for Kubernetes Staging Mirror Repositories

[sAchin-680]

Repository to update

github.com/kubernetes/staging/src/k8s.io/

What is changing?

Please disable GitHub issues for this repository.

Why is this needed?

This repository is a staging mirror of kubernetes/staging/src/k8s.io/. As per Kubernetes project conventions, all contributions - including issues and pull requests-should be directed to the main Kubernetes repository:
https://github.com/kubernetes/kubernetes

Disabling issues in this mirror repository will help reduce confusion and prevent duplication of effort.

This change follows the best practices outlined in the Kubernetes community guidelines:
kubernetes/community#8308

List of repos that are in staging/src

This change applies to the following Kubernetes staging repositories:

• https://github.com/kubernetes/api
• https://github.com/kubernetes/apiextensions-apiserver
• https://github.com/kubernetes/apimachinery
• https://github.com/kubernetes/apiserver
• https://github.com/kubernetes/cli-runtime
• https://github.com/kubernetes/client-go
• https://github.com/kubernetes/cloud-provider
• https://github.com/kubernetes/cluster-bootstrap
• https://github.com/kubernetes/code-generator
• https://github.com/kubernetes/component-base
• https://github.com/kubernetes/component-helpers
• https://github.com/kubernetes/controller-manager
• https://github.com/kubernetes/cri-api
• https://github.com/kubernetes/cri-client
• https://github.com/kubernetes/csi-translation-lib
• https://github.com/kubernetes/dynamic-resource-allocation
• https://github.com/kubernetes/endpointslice
• https://github.com/kubernetes/externaljwt
• https://github.com/kubernetes/kms
• https://github.com/kubernetes/kube-aggregator
• https://github.com/kubernetes/kube-controller-manager
• https://github.com/kubernetes/kube-proxy
• https://github.com/kubernetes/kube-scheduler
• https://github.com/kubernetes/kubectl
• https://github.com/kubernetes/kubelet
• https://github.com/kubernetes/metrics
• https://github.com/kubernetes/mount-utils
• https://github.com/kubernetes/pod-security-admission
• https://github.com/kubernetes/sample-apiserver
• https://github.com/kubernetes/sample-cli-plugin
• https://github.com/kubernetes/sample-controller

Where does it come from?

These repositories are mirrored from:
https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/

Related to

• Apply best practices to staging repos kubernetes#131315
• List the best practices on configuring staging repo community#8308

[BenTheElder]

Repository to update
github.com/kubernetes/staging/src/k8s.io/

This should be a list of repos that are in staging/src but haven't already been updated yet, like https://github.com/kubernetes/api

[sAchin-680]

This should be a list of repos that are in staging/src but haven't already been updated yet, like https://github.com/kubernetes/api

Please correct me if I'm wrong, but I believe this should be a list of repos in staging/src

[BenTheElder]

Please correct me if I'm wrong, but I believe this should be a list of repos in staging/src

The directories in staging/src are synced to repos.

The real repo names are like https://github.com/kubernetes/api (this is from staging/src/k8s.io/api)

We should provide those instead of the k8s.io/$repo aliases used only by go.

[sAchin-680]

I've updated the references to use the actual GitHub repository names like https://github.com/kubernetes/api instead of the k8s.io/$repo