Automate detection of GitHub user renames

[Okabe-Junya]

ref. https://kubernetes.slack.com/archives/C01672LSZL0/p1746110070862829

Background

When a k / k-sigs / ... member renames their GitHub login, references to their old name remain in scattered OWNERS files and config/**/org.yaml like

• https://github.com/kubernetes/org/blob/main/config/kubernetes/org.yaml
• https://github.com/kubernetes/org/blob/main/OWNERS

Relying on manual PRs or human checks to update these is error-prone and inconsistent, risking breakage of OWNERS-based automation (approvals, CODEOWNERS, etc..).

Proposal

Leverage each user's immutable GitHub numeric ID. The ID and login name can be looked up interchangeably, for example:

$ curl https://api.github.com/users/Okabe-Junya | jq .id
86868255

$ curl https://api.github.com/user/86868255 | jq .login
"Okabe-Junya"

(Where and how to store the full list of IDs <-> logins has not yet been decided.)

[Okabe-Junya]

/kind feature
/help
/cc @BenTheElder @neolit123

[k8s-ci-robot]

@Okabe-Junya:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/kind feature
/help
/cc @BenTheElder @neolit123

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.

[Okabe-Junya]

I think the data structure we need to solve this issue is simply a set.
With storing the list of IDs for each team and org member in a key-value store, we can detect any drift caused by GitHub login renames.

[pacoxu]

We were trying to build a tool to do member cleanup #2052. I am not sure if this can be used for that tool as well to avoid cleanup for renaming.(I am not sure if this part is covered by the WIP tool)