list-timers

List timers in your user scope, a team you own, or a repo you can read.

New to deferred work? Read the Timers and future signals guide or follow recurring repository maintenance.

Scope and access

  • User-scoped timers are private to the authenticated user.
  • Team-scoped timers can only be listed or managed by a team owner.
  • Repo-scoped timers can be listed and fetched by users with repo read access; creating, updating, or deleting one requires maintainer access.
  • A timer UUID is only reachable through its owning user, team, or repo scope.

Usage

pearing-cli list-timers [--team <slug>] [--repo <locator>] [--status <status>]

Omit --team and --repo for your own timers. The two scope flags conflict.

Examples

pearing-cli list-timers
pearing-cli list-timers --team platform
pearing-cli list-timers --repo teams/platform/website --status active

Response

Prints the API page JSON. status accepts active, paused, completed, or cancelled.

Errors

  • Invalid status values return a validation error.
  • Team timers require team ownership; repo timers require repo read access.

Help Output

List timers.

Timers are scoped to you, a team you own, or a repo you can read.

Examples:

  list-timers
  list-timers --team platform
  list-timers --repo teams/platform/website --status active

Usage: pearing-cli list-timers [OPTIONS]

Options:
      --team <TEAM>
          Address a team's timers. Requires team ownership

      --repo <REPO>
          Address a repo's timers. Read access is enough to list or fetch; create, update, and delete require maintainer access

      --status <STATUS>
          Filter by status

  -h, --help
          Print help (see a summary with '-h')