gplay edits begin
Open an explicit Edit on --package and persist its ID to .gplay/edit-<package>.json. While the pin exists, subsequent write commands (releases upload, tracks create, metadata apply, …) reuse the open Edit instead of opening their own — so several changes batch into one atomic transaction.
The Edit stays open until you run gplay edits commit (publish) or
gplay edits discard (abandon). There is no auto-commit and no
auto-discard in explicit mode — the lifecycle is yours.
The package defaults to the repo's .gplay/config.json pin when --package is omitted; a project (gplay init) is required since the pin lives in .gplay/. Opening a second Edit while one is already pinned is refused (exit 60).
gplay edits begin [flags]| Flag | Description |
|---|---|
--output string | output format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI) |
--package string | Android package name (overrides .gplay/config.json pin) |
Global flags
Section titled “Global flags”| Flag | Description |
|---|---|
--account string | name of a stored Account to use (overrides env and active Account) |
--retry int | retry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry) |
--service-account string | path to a service-account JSON, or inline JSON content (overrides --account, env, and active Account) |
--timeout duration | per-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads) |
-v, --verbose | log flow steps to stderr (info level) |