Import collection fails with "could not read Username" error when cloning private repository #131

New issue

Open

opened 2026-05-21 08:15:45 +00:00 by mahmoud · 0 comments

mahmoud commented

2026-05-21 08:15:45 +00:00

Owner

Description

Attempting to import a collection from https://forge.ourworld.tf/ourworld/docs_public_owh.git into the ourworld namespace fails immediately during the clone step:

Starting import of https://forge.ourworld.tf/ourworld/docs_public_owh.git into 'ourworld'...
Cloning https://forge.ourworld.tf/ourworld/docs_public_owh.git into namespace 'ourworld'...
Clone failed: Failed to clone https://forge.ourworld.tf/ourworld/docs_public_owh.git: Git operation failed: Git clone error: Cloning into '/root/code/docs_public_owh'...
fatal: could not read Username for 'https://forge.ourworld.tf': No such device or address

The repository appears to require authentication, but no credential prompt or authentication mechanism is available during the import process, causing the clone to fail outright.

Expected behavior: The import flow should support authentication for private repositories (e.g., via credentials, tokens, or SSH keys), or provide a clear error message indicating that authentication is required.

### Description Attempting to import a collection from `https://forge.ourworld.tf/ourworld/docs_public_owh.git` into the `ourworld` namespace fails immediately during the clone step: ``` Starting import of https://forge.ourworld.tf/ourworld/docs_public_owh.git into 'ourworld'... Cloning https://forge.ourworld.tf/ourworld/docs_public_owh.git into namespace 'ourworld'... Clone failed: Failed to clone https://forge.ourworld.tf/ourworld/docs_public_owh.git: Git operation failed: Git clone error: Cloning into '/root/code/docs_public_owh'... fatal: could not read Username for 'https://forge.ourworld.tf': No such device or address ``` The repository appears to require authentication, but no credential prompt or authentication mechanism is available during the import process, causing the clone to fail outright. Expected behavior: The import flow should support authentication for private repositories (e.g., via credentials, tokens, or SSH keys), or provide a clear error message indicating that authentication is required.