[windows] unable to delete an already deleted git repository
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Steps to reproduce:
- add a keybase repo as a
new-originremote - launch the command
git push --all new-originand interrupt it (CTRL-Cworks well, but could also be caused by a connectivity problem) - try to delete said keybase repository
The first deletion apparently doesn't give an error but the result is a spurious entry in the list of repositories, that can't be removed.
On the next tries to delete it it just fails with the error repository xxx doesn't exist so the entry still exsists in the list.
keybase log send id:
0c880b40e66ce74628d4d31c
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.
Research direction
Reproduce the Windows workflow with a Keybase repository added as the new-origin remote, interrupting git push --all new-origin, then attempting deletion. Trace the repository deletion and repository-list handling from that reproduction, and use the provided Keybase log ID 0c880b40e66ce74628d4d31c to compare behavior. Done means an interrupted push does not leave an undeletable repository entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100