At this level
org.tangled.repo ยท 10- org.tangled.repo.artifact record
- org.tangled.repo.createRepo procedure Create a new repository
- org.tangled.repo.declaration record Git repository declaration. Record is owned by the repository owner and record-key is slug of the git repository.
- org.tangled.repo.defs defs Metadata about the requesting account's relationship with the subject content. Only has meaningful content for authed requests.
- org.tangled.repo.deleteRepo procedure Delete a repository
- org.tangled.repo.getImportStatus query How far the knot got importing a repository from its source. Only the repository owner and knot admins see the real reason; everyone else gets a generic one.
- org.tangled.repo.listRecordVersions query Every version of a record this knot hosts, oldest first unless order says otherwise. A version's bytes are fetched by content id through com.atproto.sync.getBlocks.
- org.tangled.repo.manifest record Git repository manifest record. This record is used for git repository discovery like how `org.tangled.actor.profile` is used to find users.
- org.tangled.repo.mintToken procedure Mint a service-auth JWT whose issuer is this repo's DID, signed by the knot that owns the repo's signing key. When calling this, you'll need the same perms as git push, ie. being repo owner/collaborator/knot-admin.
- org.tangled.repo.reserveKey procedure Reserve a repo identity under a DID the caller brings. The knot seals and holds a signing key for the repo DID; the caller publishes the matching public key in that DID's document before calling org.tangled.repo.createRepo with the same DID.