krew fails to work if defaultRemoteName is assigned in ~/.gitconfig

[dustmop]

I have this config option set in my global ~/.gitconfig file:

[clone]
	defaultRemoteName = home

Which changes the default remote name to home. However, krew assumes that the default remote name is always going to be origin, due to

krew/internal/gitutil/git.go

Line 75 in efaaa22

return Exec(dir, "config", "--get", "remote.origin.url")

This causes most commands to fail:

> kubectl krew install [PACKAGE_NAME_HERE]
failed to retrieve plugin indexes: failed to list the remote URL for index default: command execution failure, output="": exit status 1

It would be better if one of the following were true:

1. krew would detect this setting and use the actual remote name
2. krew did not use this setting from the global config, perhaps by running with a blank config
3. The error message was better when GetRemoteURL returned empty data

[kundan2707]

/kind support

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[kundan2707]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ahmetb]

We can keep it open but I don't know what low % of users this actually impacts.
/lifecycle frozen