Cannot go get github.com/cli/cli/v2 v2.0.0

[heaths]

With extension support, some extensions might want to take advantage of public APIs and need to `go get github.com/cli/cli/v2@v2.0.0 but go errs:

This is apparently because go.mod needs to specify "v2" now that it has progressed to a v2 version: https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher

[vilmibm]

gh is by intention not go gettable; it is not intended to be used as a library and our Go API has no guarantees of consistency or documentation. We are working on a Go SDK for extension authors to import that will extract the parts of gh we want to expose as a public API.

[mislav]

Even though our project is not go-gettable for other reason (#1389), I do agree we should rename our module from github.com/cli/cli to github.com/cli/cli/v2 in accordance with Go's versioning guidelines that are sometimes enforced through its tooling. I've opened a PR.

[heaths]

A separate module for extension developers makes a lot of sense. Combined with #4194 having a complete solution for binary extensions would be fantastic. For example, your gh function and refactoring a bunch of the formatting code you use in your built-in commands (like I use in heaths/gh-label) would be helpful and help provide a consistent experience.

Additionally, for script developers maybe some command that gh defines that could take JSON (even invalid JSON that gh api --pageable produces, or if that was fixed for #1268 even better) and apply a --template would be great for table or other output for a consistent feel.

[heaths]

Is there already another issue open on creating a go-gettable module for extension developers? I'd love to pile on a few ideas before PR #4199 closes this.

For example, in addition to the ideas above, providing some mechanic to pass -R or --repo to override the repo as gh itself does would be great. I did that in heaths/gh-label@6742df3 (does a few more things, but mostly handling -R) which more simplistically mimics what gh does. Not hard, but seems that a "global" option like -R should just work - at least if extension developers choose to opt into that.

[vilmibm]

Ah no there is not yet an issue, but there should be! feel free to open one, @heaths . CC @samcoe since he has already started on that work.

[heaths]

#4264