workflow db-clean

Remove workflow’s local data, the databases it keeps between sessions

Synopsis

List the database files workflow keeps between sessions, with each one’s size and what it holds, then remove the cache (workflow.db) once confirmed: the last scope, what was announced and the cached issue lists, which a session makes again. –all also removes kept.db, whom each code owner is on Slack and each repository’s groups, which are then asked again. Nothing is removed under –dry-run.

workflow db-clean [flags]

Examples

  workflow db-clean --dry-run   # each file and what it holds, nothing removed
  workflow db-clean --yes       # remove the cache, unattended
  workflow db-clean --all       # also forget whom each code owner is on Slack

Options

      --all    also remove kept.db, so people and group associations are asked again
  -h, --help   help for db-clean
  -y, --yes    go ahead without the confirmation

Options inherited from parent commands

  -n, --dry-run             hold back every write to Jira, the forge, the messaging service, Taskwarrior, git and files, and say what it would have done
      --log-format FORMAT   say what goes to stderr as FORMAT: text, or json or logfmt, an entry a line stamped with its time (default text)
  -q, --quiet               say only warnings, errors and questions on stderr, leaving every note out
      --request-log FILE    append a one-line outline of each request (method, path, status, duration) to FILE, for a bug report
      --verbose             also say each request's outline on stderr, as a debug line (not while the terminal interface draws)

SEE ALSO

• workflow - Run your Jira, Git forge and messaging workflow, in the terminal or a browser