Does not work when I have existing fork with different name
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
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.
Description
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.
- Dominant language
- Python
- Stars
- 4
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from astrofrog/batchpr
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in astrofrog/batchpr
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100