Private clone

🔒 Heads up: akd-core is now private

We recently made akd-core private ahead of release. This means uv sync will hang or fail if your git auth isn't configured for non-interactive access.

You must be added to the repo first — reach out to me or another admin if you don't have access yet.

Option 1: GitHub PAT (quickest fix)

1. Create a Personal Access Token at GitHub → Settings → Developer Settings → Personal Access Tokens
   • Fine-grained token with read access to accelerated-discovery repo
2. Export it before running sync:

export UV_GITHUB_TOKEN=ghp_xxxxxxxxxxxx
uv sync

Option 2: SSH (recommended long-term)

1. Set up an SSH key with GitHub (no passphrase, so uv/git can use it non-interactively)
2. Update your pyproject.toml dependency to use SSH:

dependencies = [
    "akd @ git+ssh://git@github.com/NASA-IMPACT/accelerated-discovery.git@develop",
]

3. Then just run:

uv sync

⚠️ A note on git+ssh:// vs git+https://

If you switch your pyproject.toml to use git+ssh://, keep in mind that SSH auth is now required even if the repo becomes public again. If your SSH keys aren't configured correctly, you won't be able to clone — even a public repo.

• Private repo → git+ssh:// works great (with passphrase-disabled SSH key)
• Public repo → git+https:// is the safer default — it just works without any auth setup

So if akd-core goes public in the future, switching back to git+https:// in your toml will avoid unnecessary SSH headaches for new contributors.

Why does this happen? uv calls git under the hood but can't open an interactive login prompt — so if git doesn't already have credentials cached, it just hangs silently. Both options above ensure credentials are available non-interactively.