forgejo-contrib/forgejo-cli
20
407
Fork
You've already forked forgejo-cli
51

fj repo clone leaves behind empty repo when cloning fails #562

Open
opened 2026年07月12日 11:49:58 +02:00 by yaakov-h · 0 comments

Expected Behavior

When cloning a repo fails, I expect no repo to be left behind so that the operation can be retried.

This matches the behaviour of git clone and gh repo clone.

Actual Behavior

yaakov@Kuat /tmp> fj -H forgejo.example.com repo clone yaakov/test-repo
 Preparing...Authentication needed for https://forgejo.example.com/yaakov/test-repo.git
Username: ^C⏎ yaakov@Kuat /tmp [SIGINT]> find test-repo/
test-repo/
test-repo/.git
test-repo/.git/config
test-repo/.git/objects
test-repo/.git/objects/pack
test-repo/.git/objects/info
test-repo/.git/HEAD
test-repo/.git/info
test-repo/.git/info/exclude
test-repo/.git/description
test-repo/.git/hooks
test-repo/.git/hooks/README.sample
test-repo/.git/refs
test-repo/.git/refs/heads
test-repo/.git/refs/tags
yaakov@Kuat /tmp> fj -H forgejo.example.com repo clone yaakov/test-repo
 Preparing...Error: './test-repo' exists and is not an empty directory; class=Invalid (3); code=Exists (-4)
Location:
 src/repo.rs:1697:22
yaakov@Kuat /tmp>

Steps to Reproduce

No response

fj Version

fj v0.5.0
user agent: forgejo-cli/0.5.0 (https://codeberg.org/forgejo-contrib/forgejo-cli/)
build type: from source
 target: aarch64-apple-darwin

Forgejo Version

15.0.4+gitea-1.22.0 built with GNU Make 4.4.1, go1.26.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify

Code of Conduct

  • I agree to act in accordance with the CoC & AI Agreement.
  • This issue was not generated by an LLM, even in part.
### Expected Behavior When cloning a repo fails, I expect no repo to be left behind so that the operation can be retried. This matches the behaviour of `git clone` and `gh repo clone`. ### Actual Behavior ``` yaakov@Kuat /tmp> fj -H forgejo.example.com repo clone yaakov/test-repo Preparing...Authentication needed for https://forgejo.example.com/yaakov/test-repo.git Username: ^C⏎ yaakov@Kuat /tmp [SIGINT]> find test-repo/ test-repo/ test-repo/.git test-repo/.git/config test-repo/.git/objects test-repo/.git/objects/pack test-repo/.git/objects/info test-repo/.git/HEAD test-repo/.git/info test-repo/.git/info/exclude test-repo/.git/description test-repo/.git/hooks test-repo/.git/hooks/README.sample test-repo/.git/refs test-repo/.git/refs/heads test-repo/.git/refs/tags yaakov@Kuat /tmp> fj -H forgejo.example.com repo clone yaakov/test-repo Preparing...Error: './test-repo' exists and is not an empty directory; class=Invalid (3); code=Exists (-4) Location: src/repo.rs:1697:22 yaakov@Kuat /tmp> ``` ### Steps to Reproduce _No response_ ### `fj` Version ```text fj v0.5.0 user agent: forgejo-cli/0.5.0 (https://codeberg.org/forgejo-contrib/forgejo-cli/) build type: from source target: aarch64-apple-darwin ``` ### Forgejo Version 15.0.4+gitea-1.22.0 built with GNU Make 4.4.1, go1.26.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify ### Code of Conduct - [x] I agree to act in accordance with the CoC & AI Agreement. - [x] This issue was not generated by an LLM, even in part.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/open-5.x-lockfile
renovate/comrak-0.x
renovate/uuid-1.x-lockfile
renovate/lock-file-maintenance
docs/contributing
no-port-in-refspec
login/v16.next.forgejo.org
crates-io-publish
0.5.x
compile-time-fluent
0.4.x
localization-alias-demo
api_url_field
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.0
v0.1.1
v0.1.0
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Design
Discussion about UI/UX design
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Kind/Upstream
This is an issue with upstream software (Forgejo) that is probably not our fault
Priority
Critical
 The priority is critical
Priority
High
 The priority is high
Priority
Low
 The priority is low
Priority
Medium
 The priority is medium
Reviewed
Confirmed
 Issue has been confirmed
Reviewed
Duplicate
 This issue or pull request already exists
Reviewed
Invalid
 Invalid issue
Reviewed
Won't Fix
 This issue won't be fixed
Status
Abandoned
 Somebody has started to work on this but abandoned work
Status
Blocked
 Something is blocking this issue or pull request
Status
Need More Info
 Feedback is required to reproduce issue or to continue work
Suspicious
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo-contrib/forgejo-cli#562
Reference in a new issue
forgejo-contrib/forgejo-cli
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?