Skip to content
Pando

pando login, step 1: a code to confirm in the browser

Starts WorkOS CLI Auth. Show user_code and verification_uri (or open verification_uri_complete). Keep device_code to yourself: it is what the CLI polls with. No credential needed.

POST
https://app.gitpando.com/v1/login/device
View as Markdown

Returns

200

OK

JSON
  • device_codestringrequired
  • user_codestringrequired

    For example RRGQ-BJVS.

  • verification_uristringrequired
  • expires_inintegerrequired

    Seconds, usually 300.

  • intervalintegerrequired

    Seconds between polls, usually 5.

  • verification_uri_completeoptionalstring

503

sign_in_not_configured: WORKOS_CLIENT_ID is not set on this Worker (use the bootstrap path).

JSON
  • errorobjectrequired
    4 properties
    • codestringrequired
    • messagestringrequired
    • pathsoptionalarray ofstring
    • checksoptionalobject

      GitHub's combined status, plus the required contexts and which are missing.

      6 properties
      • shastring | nullrequired
      • statesuccessorpendingorfailureorerrorormissingorunknownrequired

        success when the merge gate passes; missing when a required context has not reported; unknown while the required checks are (an unforced merge is refused).

      • requiredarray | nullrequired

        Null while unknown.

      • checks_unknownstring | nullrequired

        Why the required checks are unknown, in plain words: "Pando couldn't read this monorepo's required checks; try again", or "pando.toml line 3: expected comma or end of structure; fix it on main, or merge with force". Null otherwise.

      • statusesarray ofobjectrequired

        The latest status per context.

        8 properties
        • shastringrequired
        • contextstringrequired
        • statependingorsuccessorfailureorerrorrequired
        • created_atstringrequired
          format: date-time
        • target_urloptionalstring | null
        • descriptionoptionalstring | null
        • creatoroptionalstring

          The member who posted it (a login); app:<slug> for a status posted with a status token or by a CI integration; hook:<hook id> for a status token from a web hook with no app.

        • appoptionalstring | null

          The CI service that reported it (buildkite, github-actions, ...), stamped by Pando from a status token or a CI integration, never from the body or target_url. Null when a member posted it with their own credential. The web shows the service's mark for a slug it knows.

      • missingoptionalarray ofstring
Navigation

Type to search…

↑↓ navigate↵ selectEsc close