Félix Baylac-Jacqué
a768efebba
git clone is creating a destination empty directory before even attempting to clone the remote URL. It means that if the user-supplied remote URL happen to be invalid, an empty directory is getting created at dest, preventing us to try cloning the same repository once again. We fixed that issue by checking whether the remote git repository exists using git ls-remote **before** calling git clone. git ls-remote will fail on a git repository not containing any git commit. We add a function to the test bed creating a git repo with one commit. It's a bit hacky, but that's the best setup I could come with. We embed a dummy git repo to the my-repo-pins codebase and copy it during the test phase to a tmp workspace. |
||
|---|---|---|
| .. | ||
| dummy-git-repo | ||
| gitea-get-request-ko.txt | ||
| gitea-get-request-ok.txt | ||
| github-get-request-ko.txt | ||
| github-get-request-ok.txt | ||