Redirected repos

Describe the bug

Renaming a repo to a repo that has previously been renamed causes repos to be merged

Version & OS

Version 2.9.0 (x64) Windows 10

Steps to reproduce the behavior

1. Set up a repo called foo and a repo called bar on GitHub, and clone these to Desktop
2. On GitHub, rename foo to foofoo and rename bar to foo.
3. On GitHub Desktop, go to the foo repo, which will rename itself foofoo
4. On GitHub Desktop, go to the bar repo, which will rename itself foo, then immediately rename itself foofoo, and associate itself with the foofoo repository.

Expected behavior

The renamed repos should remain independent

Logs

2021-06-22.desktop.production.log

In the log, I renamed Rogue → Rogue-ms, and Rogues → Rogue. I later renamed this repo Roguey on GitHub and re-checked it out into a new directory, copying changes across, but when I renamed it Rogue again, GitHub Desktop conflated it with the Rogue-ms repo.

[ms609]

Thanks! These instructions has allowed me to untangle my repos and get back to good working order.

[ms609]

@tidy-dev Thanks for the suggestions; after a few restarts, I have found myself with a duplicate entry for each repo; one duplicate still displays the behaviour described above, whilst the other works normally. Clearing “Cache storage” and “Local and session storage” didn’t change anything, but now I’ve got a workable setup I’m hesitant to start clearing more data.