Open pllim opened 3 years ago
The workaround is to rename the fork's repo name to be the same as upstream.
Or just skip these and dump them into a "manual_checks_required.txt" file or whatever. E.g. in cases of generic repo names I certainly use a different name when forking, e.g. a project
, or teams
or similar repo gets prepended with their org name or whatever is sensible at the time of forking thus I definitely don't want them to be renamed by an automated tool.
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.