Handle GitHub repositories that moved

[marco-c]

There are some GitHub repositories I moved from my personal account to the Mozilla org (e.g. marco-c/grcov -> mozilla/grcov).
The issues from those repos don't show up in codetribute (they do show up in bugsahoy).

[fiennyangeln]

I think the entry is updated in bugsahoy to mozilla/grcov thus it shows up https://github.com/jdm/bugsahoy/blob/master/magic.js#L241

[marco-c]

Bad example, I forgot I had updated that (and I guess you imported from bugsahoy before my update).

mozilla-releng/services (moved to mozilla/release-services) is a good example.

[djmitche]

I don't know how Github handles those redirects in general. It seems that whatever API bugsahoy used "followed" the redirects, whereas the GraphQL API codetribute uses does not. It may be that we just need to keep the YAML files up to date?

[hwine]

Interesting -- if you use API v3 (REST), you get a 301 with info on the new location, both in the HTTP headers and the JSON response.

With API v4 (GraphQL), you only get a 404 :(

fwiw, I opened a ticket on GitHub's GraphQL support forum.

[hwine]

Looks like no support for detecting renames in GraphQL (no action on ticket)

Up to the frontend infra team how they want to handle this case, imo. One way to minimize ongoing breakage would be to restrict use of this tool to repositories already in a Mozilla owned org.

[fiennyangeln]

Or maybe we can add a sentence in the README in the Github section that they need to keep their repository org and name up to date as Dustin previously suggested?

[jdm]

Maybe some kind of nightly job that queries all of the repositories and checks that they still resolve would be the easiest way to deal with this.