Discovering repositories

List namespaces and repositories, and fetch a single repository.

Use namespaces.list to enumerate the containers you can access, then repos.list / repos.listAll to walk their repositories, and repos.get to fetch a single normalized Repository.

Namespaces

A namespace is the container a repository lives in. Each provider names them differently; repo-sdk normalizes them to a Namespace with a kind telling you which one you’re looking at.

To resolve the account behind the credentials themselves, use users.me() — see Who is this token? in the authentication guide.

const { data: namespaces } = await client.namespaces.list();

// Or iterate every namespace across all pages:
for await (const namespace of client.namespaces.listAll()) {
  console.log(namespace.kind, namespace.slug);
}

Listing repositories

repos.list returns one Page<Repository>; repos.listAll follows cursors and yields every repository. Both accept the same filters:

// Everything you can access:
for await (const repo of client.repos.listAll()) {
  console.log(repo.path);
}

// Scoped to one namespace:
const { data } = await client.repos.list({ namespace: 'capawesome-team' });

// Search by name (where supported):
const { data: hits } = await client.repos.list({ query: 'sdk' });

Fetching a single repository

repos.get takes a repo string in the provider’s native path form and returns the normalized Repository:

const repo = await client.repos.get({ repo: 'capawesome-team/repo-sdk' });
repo.defaultBranch; // normalized
repo.urls.cloneHttp; // normalized
repo.raw; // untouched provider payload

The repo string per provider