Broken link in README of sig-autoscaling

kubernetes / community

Kubernetes community content

Apache License 2.0

11.98k stars 5.17k forks source link

Broken link in README of sig-autoscaling #5663

Open MadhavJivrajani opened 3 years ago

MadhavJivrajani commented 3 years ago

The link for Owners in client-go/scale seems to be broken due to a missing OWNERS file in the scale directory.

MadhavJivrajani commented 3 years ago

/sig autoscaling

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

MadhavJivrajani commented 3 years ago

/remove-lifecycle stale

akuzni2 commented 3 years ago

/assign

akuzni2 commented 3 years ago

According to the owners file under k/client-go the whole repo belongs to sig-apimachinery. Should I just remove the readme reference to scale being a subproject since it looks like the entirety of k/client-go belongs to a different sig?

Please correct me if I'm wrong here thanks

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue or PR as fresh with /remove-lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

MadhavJivrajani commented 2 years ago

/remove-lifecycle rotten /lifecycle frozen

spzala commented 2 years ago

scale is a special parts of client-go but since it's not a repo on its own, the link should point to the OWNERS of the client-go