go-contrib-init error message

[Patrick]

Hello all,

I'd like to contribute to https://go.googlesource.com/text. So I cloned the directory and ran (after registering and logging in)

go-contrib-init

and the resulting message is:

Current directory's git was cloned from "https://go.googlesource.com/text"; origin should be "https://go.googlesource.com/go"

The git remote is 

[remote "origin"]
url = https://go.googlesource.com/text

fetch = +refs/heads/*:refs/remotes/origin/*

Any idea if this is a fatal error message or what I can do?

Thank you 

Patrick 

[Ian Lance Taylor]

go-contrib-init has a -repo option. In this case you should run
"go-contrib-init -repo=tools".

Thanks for your interest in Go.

Ian

[Patrick]

> go-contrib-init has a -repo option. In this case you should run
> "go-contrib-init -repo=tools".

Thank you, Ian.

This gives me (with -repo=text)

$ go-contrib-init -repo=text
The repo you want to work on is currently not on your system.
Run "go get -d golang.org/x/text" to obtain this repo
then go to the directory "/Users/patrick/go/src/golang.org/x/text"

following the text gives me

$ go get -d golang.org/x/text
go: -d flag is deprecated. -d=true is a no-op
go: go.mod file not found in current directory or any parent directory.
'go get' is no longer supported outside a module.
To build and install a command, use 'go install' with a version,
like 'go install example.com/cmd@latest'
For more information, see https://golang.org/doc/go-get-install-deprecation
or run 'go help get' or 'go help install'.

 

So I don't know how to proceed. IMO the error message for the problem I had in the first message should include the possibility to change the repo and the second error message seems misleading.

Meanwhile I have created a pull-request without go-contrib. 

Thank you very much for your answer.

 Patrick

[Ian Lance Taylor]

Sorry about the difficulties. Would you be willing to open an issue
about this at https://go.dev/issue? Thanks.

Ian

[Patrick]

Sorry about the difficulties. Would you be willing to open an issue 
about this at https://go.dev/issue? Thanks.

https://github.com/golang/go/issues/72773 

Thank you very much for your time. I'd be happy to provide more information or change the bug report if necessary.

Patrick