overlane github repositories

Lists the repositories the installation can see, public and private, as owner/name. The installation must be one of the team’s, from overlane github installations. GitHub is asked each time, so a repository added there shows up at once.

Usage

overlane github repositories installation-id [--service URL] [--team TENANT_ID]

Arguments

Argument	Required	Description
`installation-id`	yes	The installation number from `overlane github installations`

Flags

Flag	Type	Required	Default	Description
`--service`	string	no		The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service)
`--team`	string	no		The team (tenant) to act on (default: the one your token belongs to)

Examples

overlane github repositories 4242
overlane github repositories 4242 --json

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: yes.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema github repositories.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "owner": {
        "type": "string",
        "minLength": 1
      },
      "name": {
        "type": "string",
        "minLength": 1
      },
      "private": {
        "type": "boolean"
      }
    },
    "required": [
      "owner",
      "name",
      "private"
    ],
    "additionalProperties": false
  }
}

See exit codes for the status the process returns.