repos

The repositories you can create an application from.

The list belongs to the person whose token this is rather than to the team, so two members of one team can see different repositories.

Connecting is granted on GitHub rather than here, and the address is printed on every run, not only when the list comes back empty. The usual problem is one repository missing from a list that already has others in it, and it is fixed at the same address.

Usage

outplane repos [flags]

Also available as outplane repo.

Flags

The global flags apply as well.

Output

Examples

List the repositories you can deploy

outplane repos

Find one by name

outplane repos --search checkout

Take just the names, for a script

outplane repos --json --fields fullName,defaultBranch

{
  "items": [
    {
      "defaultBranch": "main",
      "fullName": "acme/checkout"
    }
  ],
  "total": 1,
  "truncated": false
}

What to Know

• The list belongs to the user who created the token, not to the team. Two members of one team can see different repositories here, and each can only create applications from their own.
• Everything is returned in one response. The endpoint's paging arguments are applied per connection and concatenated, so they cannot be used, and this command does not offer them.
• An empty list means nothing is connected yet, not that the account has no repositories. Connecting happens in a browser and cannot be done from here; the address is in the error and in every successful run.
• A repository missing from a non-empty list needs its access granting at the same address. That is the usual case, not the empty one.
• Repositories that are disabled upstream are left out, because they cannot be cloned and so could never build. Archived ones are listed and marked.

Errors

Beyond 0 for success, this command exits with:

The code on the error object is one of repos.not_connected, auth.not_authenticated. Branch on that, or on the exit status. The message is prose and changes.

Related