gplay-cli-usage

gplay CLI conventions (foundation)

Conventions shared by every gplay command; the normative source is docs/DESIGN.md in the CLI repo. --help wins over this skill when they disagree:

gplay --help                       # the whole command tree
gplay <group> --help               # a namespace (releases, tracks, team, …)
gplay <group> <command> --help     # one command, with its real flags
gplay exit-codes                   # the semantic exit-code table + diagnostic codes

Stability: the [experimental] banner

gplay is GA. A command whose --help opens with [experimental] sits outside the Public contract (pin an exact release in CI, the banner says so); every other surface holds until a major bump, so CI can pin v1 (stability).

gplay schema: the offline API map

Where --help documents gplay's own surface, gplay schema <query> introspects the Android Publisher API offline (no credential, no HTTP): methods, REST paths, types, enums. [experimental]; flags in gplay schema --help.

gplay schema edits.tracks.update    # a method's request/response, one hop deep
gplay schema Track                  # a type's fields, types, enums
gplay schema --command "releases upload"   # the API methods a gplay command calls

Which credential

Highest priority first: --service-account <path-or-inline-JSON>, --account <name>, GPLAY_SERVICE_ACCOUNT (path or inline JSON), then the active stored Account (gplay auth login). Setup and diagnosis of exits 10/11: gplay-setup.

Which app (--package + project pinning)

Most commands need a target package. Resolution (ADR-0004):

1. --package com.example.app on the command, else
2. the package pinned in .gplay/config.json for the current repo.

Pin once with gplay init (or gplay apps init) so day-to-day commands need no --package. Managing the registry of packages is the gplay-apps skill.