CLI is not go install-able

[marwan-at-work]

Due to the replace clause in the go.mod file of this repository, go get fails with the following errors:

go: found github.com/cli/cli/cmd/gh in github.com/cli/cli v0.11.0
# github.com/cli/cli/api
go/pkg/mod/github.com/cli/cli@v0.11.0/api/queries_issue.go:393:12: gql.MutateNamed undefined (type *graphql.Client has no field or method MutateNamed)
go/pkg/mod/github.com/cli/cli@v0.11.0/api/queries_issue.go:418:12: gql.MutateNamed undefined (type *graphql.Client has no field or method MutateNamed)
go/pkg/mod/github.com/cli/cli@v0.11.0/api/queries_repo.go:148:12: too many errors

I highly recommend either removing this replace clause here either by contributing the changes upstream or forking the repo and changing the import path.

Thanks!

[AliabbasMerchant]

AFAIK, we are just focussing on being a command line program, and not a library/dependency/module for any external program, so go getting cli would not make sense

[marwan-at-work]

@AliabbasMerchant just FYI I wasn't trying to use it as a library or dependency. Go get is a common way to download and install Go programs that are executed as a binary

[AliabbasMerchant]

Oh. Okay 👍

[Uzume]

The repo is already forked but there is another issue: cli/shurcooL-graphql@89ab2a8.

The added go.mod declares its module as github.com/shurcooL/graphql so it cannot be directly required as cli/shurcooL-graphql, thus the need for the replace directive here.

I created a pull request to get this fixed as referenced above.

Directly trying to push these kinds of changes upstream is already in progress, see:

• updated to modules shurcooL/graphql#53
• Add support for named GraphQL operations shurcooL/graphql#57

[rogpeppe]

This issue prevents gh from being installed directly by using Go 1.16's go install:

% go install github.com/cli/cli/cmd/gh@v1.9.2
go: downloading github.com/cli/cli v1.9.2
go install: github.com/cli/cli/cmd/gh@v1.9.2 (in github.com/cli/cli@v1.9.2):
  The go.mod file for the module providing named packages contains one or
  more replace directives. It must not contain directives that would cause
  it to be interpreted differently than if it were the main module.

Given that it looks like the graphql upstream isn't being updated, and that the cli repository doesn't depend on anything external that itself depends on the graphql repository, it seems like it would be a reasonable idea to hard fork it, replacing all import paths as necessary.

[mislav]

@rogpeppe You are right; our upstream changes to graphql package are unlikely to get merged and we should hard-fork this dependency instead.