workflow doctor

Report the repository, tooling, and configuration in effect

Synopsis

Report the git repository this session is in, which external programs are installed, where the store keeps its files — or why it keeps none — which .workflow.json is in effect, and which required fields are still empty.

Makes no network calls by default, so it is safe to run anywhere and tells you only that a credential is present. Add –online to ask Jira, your forge and Slack whether each credential works; a webhook is left unchecked. Add –json for the same facts as data, with the same masking.

workflow doctor [flags]

Examples

  workflow doctor --online                              # ask each service whether its credential works
  workflow --request-log requests.log doctor --online   # a bug report's evidence

Options

  -h, --help[=true|false]     help for doctor
  -j, --json[=true|false]     print the report as JSON
      --online[=true|false]   ask Jira, the forge and Slack if each credential works (not a webhook)

Options inherited from parent commands

  -n, --dry-run[=true|false]   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[=true|false]     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[=true|false]   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