7 Commits

Author	SHA1	Message	Date
Mike Pountney	ba7cc13145	Switch over to using github.com/go-jira/jira, from gopkg.in ... There should be no reason to use gopkg.in versioned imports now that we're using go modules. I think, IANAE. gopkg.in kind of gets in the way of modules, as it only pulls over tagged releases from github.com -- this then means that you need to use go modules 'replace' syntax in the go.mod to use a non-versioned commit or branch. This is feasible, but kind of ugly. go modules defaults to pulling the latest version, so the default behavior is the same as when pulling go-jira.v1 from gopkg.in.	2019-10-01 21:29:46 -07:00
CodeLingo Bot	3cf2e56e1f	Fix function comments based on best practices from Effective Go ... Signed-off-by: CodeLingo Bot <bot@codelingo.io>	2019-10-01 21:29:45 -07:00
Cory Bennett	9146346e2f	[#163] fix url path join logic	2018-04-15 16:56:09 -07:00
Cory Bennett	c226077320	add --quiet global option	2017-09-04 18:12:32 -07:00
Cory Bennett	c0358eb67c	refactor to allow for --insecure and --unixproxy arguments	2017-09-04 17:53:01 -07:00
Cory Bennett	979da1f3a5	refactor for GlobalOptions and CommonOptions	2017-09-02 14:05:27 -07:00
Cory Bennett	0a5510b231	move commands from jiracli package to jiracmd package	2017-09-02 09:14:54 -07:00