`forked-to` only works on some repositories

Out of 31 source repos of the forks I have on my account, only on 3 of them (funnily, refined-github is one of them) forked-to seems to work. Example repo where it doesn’t work: https://github.com/Cog-Creators/Red-DiscordBot Screenshot:

[Jackenmen]

@fregante Ah, that makes sense. I checked the local storage and cache works (not a lot of entries since I cleared the cache 2 days ago/yesterday):

cache:forked-to:jack1142@Cog-Creators/Red-DiscordBot:
data: ["jack1142/red-discordbot"]
maxAge: 1585402612639
__proto__: Object

cache:forked-to:jack1142@jelmer/python-fastimport:
data: ["jack1142/python-fastimport"]
maxAge: 1585336802470
__proto__: Object

cache:forked-to:jack1142@sindresorhus/refined-github:
data: ["jack1142/refined-github"]
maxAge: 1585402706428
__proto__: Object

So looks like the problem here is that the repo key should be lowercase (I manually added lowercase cache entry and now the fork link works)

[fregante]

If after following those instructions you don’t see the link to the fork added to the source repo, it may be because:

• the fork isn’t being remembered
• the fork isn’t being associated to the right source (<- most likely)
• the DOM has changed (it should throw an error)

Try this in the background page:

await browser.storage.local.get()

And look for something like cache:forked-to:cog-creators/red-discordbot

It can help you understand why it’s not being associated correctly.