KEP-5905: Migrate kubernetes-mixin from kubernetes-monitoring to kubernetes-sigs organization#5906
KEP-5905: Migrate kubernetes-mixin from kubernetes-monitoring to kubernetes-sigs organization#5906rexagod wants to merge 2 commits intokubernetes:masterfrom
kubernetes-mixin from kubernetes-monitoring to kubernetes-sigs organization#5906Conversation
k8s-ci-robot
added
cncf-cla: yes
k8s-ci-robot
added
the
sig/instrumentation
k8s-ci-robot
added
approved
…`kubernetes-sigs` organization This KEP aims to migrate `kubernetes-monitoring/kubernetes-mixin` repository under the `kubernetes-sigs` organization. More importantly, it aims to foster better collaboration and maintenance for the repository within the Kubernetes ecosystem as a direct consequence.
k8s-ci-robot
removed
the
approved
skl
left a comment
skl
left a comment
There was a problem hiding this comment.
lgtm, happy to help where I can as this progresses!
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rexagod, skl The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| with the same level of quality and reliability. To not break existing | ||
| references, CI automations will be setup in the `kubernetes-monitoring` | ||
| counterpart, to enable mirroring changes from the `kubernetes-sigs` repository. |
There was a problem hiding this comment.
you should be able to transfer the repository to the new organization, and it will redirect all previous links. All current Issues / Pull Requests /etc will stay open, and any git clone/fetch/push operations should be redirected as well. At least that's what the documentation says:
- When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved
- All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL
There was a problem hiding this comment.
I'd prefer explicitly archiving it and mentioning the updated source (k-sigs) there, so any community or unofficial mixin repository in the far future with the same name doesn't break the redirects.
If you create a new repository or fork at the previous repository location, the redirects to the transferred repository will be permanently deleted.
…ng` to `kubernetes-sigs` organization
4 participants
kubernetes-monitoring/kubernetes-mixinrepository under thekubernetes-sigsorganization and aims to foster better collaboration and maintenance for the repository within the Kubernetes ecosystem as a direct consequence.kubernetes-mixinfromkubernetes-monitoringtokubernetes-sigsorganization #5905