Skip to main content
The blacksmith stickydisk commands let you inspect and delete a repository’s sticky disks programmatically.

Permissions

Listing requires the user who created the CLI token to be able to see the target repository on GitHub (any permission level, including read) — the same visibility rule the dashboard enforces. For org-scoped sticky disks (such as container caching), access to any repository in the organization suffices for listing. Deleting additionally requires the user who created the CLI token (via blacksmith auth login) to have write access to the target repository on GitHub (the WRITE, MAINTAIN, or ADMIN role) — the same rule the dashboard enforces. For org-scoped sticky disks (such as container caching), write access to any repository in the organization suffices. Tokens not tied to a user account cannot delete; re-authenticate with blacksmith auth login to mint a token tied to your account. Organization tokens are exempt from these per-repository checks and can list and delete for any repository in the organization.

blacksmith stickydisk list

Lists sticky disks for a repository.

blacksmith stickydisk delete

Deletes all sticky disks for a repository that exactly match --key. By default every architecture variant of the key is deleted; narrow the selection with --arch.
Deleting a sticky disk is safe: the next job that requests the key starts from an empty disk and repopulates it, the same as a cold cache.