Command Line Interface¶
bugwarrior pull¶
Pull down tasks from forges and add them to your taskwarrior tasks.
Relies on configuration file.
Usage
bugwarrior pull [OPTIONS]
Options
- --dry-run¶
- --flavor <flavor>¶
The flavor to use
- --interactive¶
Deprecated. Interactive mode is now detected automatically via isatty().
- --debug¶
Do not use multiprocessing (which breaks pdb).
- --quiet¶
Set logging level to WARNING.
bugwarrior uda¶
List bugwarrior-managed uda’s.
Most services define a set of UDAs in which bugwarrior store extra information about the incoming ticket. Usually, this includes things like the title of the ticket and its URL, but some services provide an extensive amount of metadata. See each service’s documentation for more information.
For using this data in reports, it is recommended that you add these UDA
definitions to your taskrc file. You can add the output of this command
verbatim to your taskrc file if you would like Taskwarrior to know the
human-readable name and data type for the defined UDAs.
Note
Not adding those lines to your taskrc file will have no negative
effects aside from Taskwarrior not knowing the human-readable name for the
field, but depending on what version of Taskwarrior you are using, it
may prevent you from changing the values of those fields or using them
in filter expressions.
Usage
bugwarrior uda [OPTIONS]
Options
- --flavor <flavor>¶
The flavor to use
bugwarrior vault¶
Password/keyring management for bugwarrior.
If you use the keyring password oracle in your bugwarrior config, this tool can be used to manage your keyring. This feature requires the optional keyring library. (pip install “bugwarrior[keyring]”)
Usage
bugwarrior vault [OPTIONS] COMMAND [ARGS]...
clear¶
Usage
bugwarrior vault clear [OPTIONS] TARGET USERNAME
Arguments
- TARGET¶
Required argument
- USERNAME¶
Required argument
list¶
Usage
bugwarrior vault list [OPTIONS]
set¶
Usage
bugwarrior vault set [OPTIONS] TARGET USERNAME
Arguments
- TARGET¶
Required argument
- USERNAME¶
Required argument
Configuration files¶
Bugwarrior will look at the following paths and read its configuration from the first existing file in this order:
the value of $BUGWARRIORRC if set
$XDG_CONFIG_HOME/bugwarrior/bugwarriorrc if exists
$XDG_CONFIG_HOME/bugwarrior/bugwarrior.toml if exists
~/.bugwarriorrc if exists
~/.bugwarrior.toml if exists
<dir>/bugwarrior/bugwarriorrc if exists, for dir in $XDG_CONFIG_DIRS
<dir>/bugwarrior/bugwarrior.toml if exists, for dir in $XDG_CONFIG_DIRS
$XDG_CONFIG_HOME/bugwarrior/bugwarriorrc otherwise