You start go get in the background, then while it is running cd up one directory and delete the CWD that git (forked from go get) is running in.

I understand that go get will be checking out into a different location, but I don't think it is unreasonable for git to assume that it's cwd will remain valid while it's doing a checkout.

I don't believe that there is anything to fix in the go tool for the bug you've reported, but I get a feeling that this is a reproduction of a different issue that you're trying to solve. Can you explain more about how you discovered this issue.

Sure thing. I accidentally cloned a repo to the wrong location instead of using go get and when I realized this, I used go get instead (in the repo I accidentally cloned) to fetch the repo into my GOPATH. Meanwhile in another terminal I decided to clean up the mis-cloned repo, resulting in this error.

git is looking for the cwd in order to convert the relative paths to absolute. In the case of go get, we are already working with absolute paths. If the fix takes only setting an env variable such as GIT_DIR, we don't have to expose the reported limitation to the go-get users. Having said that, I haven't yet find a quick fix.

@rakyll go get forks git in the current working directory. It could equally fork git in $GOPATH/src or another location that should exist.

Having said that, I'm unconvinced this is a bug or should be fixed. If you don't want git to complain that the working directory is missing, don't delete it behind git's back.

@davecheney To be more clear, I don't understand why go get is cloning in the current directory. go get is a tool to download packages to a certain destination that is not tied to the cwd. I am not quite convinced the current case shouldn't be improved even though I'd say it is not critical enough to care.

Go get isn't cloning in the current directory, git is, because the go tool
didn't change the directory to anything else yet. I'm sure we can fix that.

On Tue, Jan 26, 2016 at 1:54 PM, Burcu Dogan notifications@github.com
wrote:

@davecheney https://github.com/davecheney To be more clear, I don't
understand why go get is cloning in the current directory. go get is a tool
to download packages to a certain destination that is not tied to the cwd.
I am not quite convinced the current case shouldn't be improved even though
I'd say it is not critical enough to care.

—
Reply to this email directly or view it on GitHub
#14093 (comment).

Go get isn't cloning in the current directory, git is,

Sorry for the implicit wording, this is what I meant above. I am talking about cd'ing into GOPATH (or setting an env variable if possible) to make git clone in a directory that makes sense.

Sounds good to me.

On Tue, Jan 26, 2016 at 2:15 PM, Burcu Dogan notifications@github.com
wrote:

Go get isn't cloning in the current directory, git is,

Sorry for the implicit wording, this is what I meant above. I am talking
about cd'ing into GOPATH (or setting an env variable if possible) to make
git clone in a directory that makes sense.

—
Reply to this email directly or view it on GitHub
#14093 (comment).

I don't think it's worth putting a workaround in here; many Unix programs including "go get" become unhappy if their working directory goes away while they are running. "Don't do that."