options: list This is the list of possible option flags that the command will accept.Then if you wanted jira foo baz to be called by default when you type jira foo you would set default: true for that custom command. If you wanted to have jira foo bar and jira foo baz you would have two commands with name: foo bar and name: foo baz. default: bool Use this for compound command groups.Sometimes useful for constructing complex commands where one custom command might call another. hidden: bool This command will be hidden from users, but still executable.help: string This is help message displayed in the usage for the command.name: string This is the command name, so for jira foobar you would have name: foobar.Where the individual commands are maps with these keys: You can do this with by creating a configuration under your project workspace at. For example, if you are working on a "foo" project and you cd into your project workspace, wouldn't it be nice if jira ls automatically knew to list only issues related to the "foo" project? Likewise when you cd to the "bar" project then jira ls should only list issues related to "bar" project. The complicated configuration hierarchy is used because go-jira attempts to be context aware. Properties overridden with command line options will have final precedence. The configuration properties found in a file closest to your current working directory will have precedence. jira.d/list.yml) then it will merge in any properties from the config.yml if found. jira.d directories discovered go-jira will load a. If your current directory is not a child directory of your homedir, then your homedir will also be inspected for a. When loading the configuration from disk it will recursively look through all parent directories in your current path looking for a. profile (assuming go-jira binary is already in your path) will cause jira to offer tab completion behavior. Since go-jira is built with the "kingpin" golang command line library we support bash/zsh shell completion automatically:įor example, in bash, adding something along the lines of: It should then be available in $GOPATH/bin/jira. This will checkout this repository into $GOPATH/src//go-jira/jira/, build, and install it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |