basemodo deploys
List an App's Deploys, newest first, each with who made it and what it changed.
basemodo deploys [OPTIONS]Its Deploy history, Rollbacks included, to choose one to roll back to or to compare (basemodo diff), 30 at a time: --before the oldest one listed gives the 30 before it. Each Deploy names its author: the Owner or an Editor who deployed or rolled back from their own account, a push to the App's linked GitHub repository, or Basemodo (rebuilding the App for a Security Update). A Deploy made before Basemodo recorded authors has none. Each new Deploy of code says what it changed in one line (its description) and in counts of files and lines; a Rollback or a Security Update changes no code. A Deploy whose code is no longer kept says so.
Arguments
--app <APP>: The App whose Deploys to list. Default: the one named after the current folder.--before <DEPLOY>: List the Deploys older than this one: thebeforeof the page listed last.
Like every command, it also takes the global options --json and --api-url.
Examples
List the Deploys of the App of this folder:
basemodo deploysList the ones before the oldest of that list:
basemodo deploys --before 0b8f6a52-3f0e-4c1e-9a57-5d1c2e7f9a10List another App's, for a script:
basemodo deploys --app lunch-rota --jsonOutput
With --json, it prints {"deploys": [{"id", "app", "status", "url", "rollback_of" (for a Rollback), "commit" (for a push), "author": {"kind" (person, push or basemodo), "email" (for a person)} or null when not recorded, "description", "changes": {"files_added", "files_changed", "files_removed", "lines_added", "lines_removed"} (for a Deploy of new code), "code_dropped_at" (when its code stopped being kept, so diff cannot compare it), "image_deleted" (true when its image was deleted, so a Rollback to it needs a new build), "created_at", "finished_at", "failure", "detection", ...}], as deploy prints each one, and "before": the id to pass as --before for the next page, when there is one.
From an agent
Basemodo's MCP serves it as the tool deploys. It only reads, so an agent's client may run it without asking you. Its arguments are the command's, named as JSON keys: app (text), before (text). It answers what the command prints with --json.