dev.knotless.createOrgRepo

Makes the repository as `knotless repo create` does: public unless asked for private, naming the runners given or those the gateway's appview offers, with no branches until the first push.

Details · procedure
Kindprocedure
Authorityknotless.dev
Indexed

Procedure

procedure · POST

Input

application/json

The branch its HEAD names, without refs/heads/: main when absent.

  • maxLength: 255

What the repository is, shown under its name.

  • maxLength: 3000
  • maxGraphemes: 300

name

requiredstring

The repository's name, its record key.

  • maxLength: 100

org

requiredstring · did

The organization.

private

boolean

Whether to make it private: a space of its own on the organization's PDS, which only its members read. Public when absent.

runners

array

The accounts that run its workflows: those the gateway's appview offers when absent.

  • maxLength: 20
itemsref
Reference

Output

application/json

members

requiredarray

The members of the organization who may push to it: on a public one, those anyone may see.

itemsref
Reference

runners

requiredarray

Its runners: a private one's can read it.

itemsref
Reference

uninvited

string

Why a private one's runners were not told of it, when they were not.

  • maxLength: 3000

#account

object

An account, by DID.

Properties

did

requiredstring · did

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Creates a repository in the account logged in to this appview's pages.

  • Create a new repository

  • Lets an account push to a repository, or read a private one.

  • That an account is an organization on knotless.

  • A private repository on knotless, keyed by its name, with its owner as its authority. Its members alone read it. The owner's records of the repository are in their repo in the space, as a public repository's are in their public repo, and so are their requests that its runners run its workflows again or cancel them; each member writes their pulls, issues, comments, reactions, labels and assignments in theirs, and a runner its checks, so that what is said of the code is as private as the code. Its