workflow config init
Set up the configuration file, asking for the Jira token and a Slack webhook and checking the Jira token
Synopsis
Ask for the Jira address and token and a Slack incoming webhook, check the Jira token, and write a .workflow.json with what passed. The webhook is saved unchecked, since a webhook cannot be checked without posting.
By default it lands at the repository root, so every subdirectory sees it; outside a repository it lands in the current directory. Use –global to write it to your home directory instead, where every directory can see it. Use –template to write a blank file to fill in by hand rather than being asked. With –dry-run it runs the same checks, writes nothing and stores nothing in the keychain, and prints the file it would write, masked.
workflow config init [flags]Examples
workflow config init # answer the prompts, the Jira token checked
workflow config init --template # a blank file to fill in by hand
workflow config init --global # one file in your home, for every directoryOptions
--force[=true|false] overwrite an existing file
--global[=true|false] write to the home directory instead of here
-h, --help[=true|false] help for init
--template[=true|false] write a blank file to edit by hand instead of being askedOptions 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 config - Create and inspect the configuration file