Some of the links are not working in sig auth folder

[AmarNathChary]

Describe the issue

This is a Bug report

Some of the links are not working in some folders like in sig auth

in authenticators Owners: link to kubernetes/kubernetes/staging/src/k8s.io/client-go/listers/authentication is not working.
in authorizers kubernetes/kubernetes/staging/src/k8s.io/client-go/listers/authorization is not working .

How can we resolve this
we can remove the unnecessary links that are not working.

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[AmarNathChary]

/kind bug

[AmarNathChary]

Also in policy-managment under Owners:
kubernetes/kubernetes/pkg/security/podsecuritypolicy
kubernetes/kubernetes/plugin/pkg/admission/security/podsecuritypolicy

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[AmarNathChary]

I am closing this issue

[AmarNathChary]

/close

[k8s-ci-robot]

@AmarNathChary: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.