workflow status
Print the current work’s issue, stage and CI on one line
Synopsis
Print, on one line, the issue the branch is for, how far along the loop the work has got, and how CI stands — the same progress the interface’s top row shows, for a shell prompt or a status bar. –json prints it as data; –plain draws its marks, and the live line it keeps on a terminal while it reads named directories, in ASCII, as ui.ascii does, for this run alone. A service that refuses to answer leaves its stage as though there were nothing to say — CI none — and is named on standard error, one line each; so is one that is not set up, such as a forge with no token, with how to set it up.
Given one or more directories, it prints a line for each, labeled with its
name, or with its path where two share a name, so workflow status ~/src/*
reports every repository at once. Each reads its own configuration. A
directory that cannot be read still gets its line, saying why, and the
command then fails, as it does outside a repository: it exits 3 when a
directory’s configuration does not load, otherwise 4 when one is not a git
repository — as bare status exits 4 outside one — otherwise 1.
workflow status [directory...] [flags]Examples
workflow status --json # where the work stands, as data
workflow status ~/src/* # every repository at once, a line eachOptions
-h, --help[=true|false] help for status
-j, --json[=true|false] print the status as JSON
--plain[=true|false] draw the line's marks, and the live line's, in ASCII, as ui.ascii does, whatever the configuration saysOptions 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