Repositories

A repository lives in a workspace. A slug is unique inside a workspace and not across them, so a slug that several workspaces hold asks for --workspace <id>. Each command uses the environment that the last district login recorded, the one an environment flag names, or production.

district repo create

district repo create <name> [--slug <slug>] [--description <text>] [--workspace <id>] [--clone] [--production | --staging | --dev]

Creates a repository and prints its slug, repo_ id and HTTPS git remote URL on stdout. The repository is created in the workspace the caller can open. A caller who can open several workspaces names one with --workspace <id>, and the error lists them.

Without --slug, district-api derives the slug from the name. A slug that a live repository of the workspace already uses is refused with the API's message.

--clone then clones into ./<slug> without asking. Without --clone, an interactive session asks Clone into ./<slug>? [Y/n], and an empty answer clones. A session with no terminal prints the git clone command to run instead, because an agent cannot answer. The clone never asks for a password: without the helper, git fails at once and the message names the fix, district git-credential install.

Arguments

Flags

Output

$ district repo create "My App" --clone
created my-app (repo_01K4…)
remote https://…/repo_01K4….git
cloning into ./my-app

Exit codes

district repo list

district repo list [--workspace <id>] [--first <n>] [--json] [--production | --staging | --dev]

Prints a header row, then one row per repository of one workspace, most recent activity first: the slug, the repo_ id, the display name, the kind, and when it was created. No clone is read: the list belongs to a workspace, not to the directory the command runs in.

The workspace is the one the caller can open. A caller who can open several workspaces names one with --workspace <id>, and the error lists them.

A repository that belongs to an applet is not listed: the applet owns it and deletes it with itself. A workspace with no repository prints nothing and exits 0.

Flags

Output

$ district repo list
SLUG       REPOSITORY                       NAME       KIND        CREATED
my-app     repo_01K4X0J8W1QZ5B7N3G2R6TQ9YD  My App     hosted_app  2026-08-25T09:00:00Z
shopfront  repo_01K4X0J8W1QZ5B7N3G2R6TQ9YE  Shopfront  hosted_app  2026-08-24T09:00:00Z

Exit codes

district repo clone

district repo clone <repository> [<directory>] [--workspace <id>] [--production | --staging | --dev]

Resolves a repository by repo_ id or by slug and runs git clone into <directory>, or into ./<slug> without one.

Authentication comes from the installed credential helper, not from the URL. The clone never asks for a password: without the helper, git fails at once and the message names district git-credential install.

Arguments

Flags

Output

$ district repo clone my-app
cloning into ./my-app
Cloning into 'my-app'...

Exit codes

district repo url

district repo url <repository> [--workspace <id>] [--production | --staging | --dev]

Prints only the repository's HTTPS git remote URL on stdout. It can be used in command substitution. The URL contains the repository id, not its slug, and does not change.

Arguments

Flags

Output

git clone "$(district repo url my-app)"

Exit codes

district repo delete

district repo delete <repository> [--workspace <id>] [--yes] [--production | --staging | --dev]

Hides a repository, its remote and every branch it holds for 14 days. The slug stays held. A restoreDeletion call with the printed deletion ID brings them back until the printed time. The purge after the printed time deletes the repository and its remote. The command prints the resolved repository and the environment, then asks Delete <slug>? [y/N].

The repository argument is required, and the clone in the current directory never names it: a command line that named nothing would otherwise delete the remote of the checkout the person is standing in.

A repository that a hosted app, a board or a routine still uses is refused with the API's message, which names the resource to delete first. district app delete removes the app. A member with resource:delete in the workspace can delete a shared repository; only the owner can delete a private one. Every other caller is told the repository was not found.

Arguments

Flags

Output

$ district repo delete my-app --yes
deleted my-app (repo_01K4X0J8W1QZ5B7N3G2R6TQ9YD, deletion del_01K4…, restorable until 2026-09-08T09:00:00Z)

Exit codes