Does not work when I have existing fork with different name

When this is run and the upstream repo name is different from my fork's repo name, say, upstream renamed it since I last forked it, I get this error: `An error occurred when cloning fork - skipping repository`

The workaround is to rename the fork's repo name to be the same as upstream.

No file or test is named in the report. Reproduce the failure with an upstream repository and a fork whose names differ, then trace the fork-cloning path and its error handling. Done means the existing differently named fork is cloned and processed without requiring a rename.

Written by the indexing model from the issue text.