William Martin

Alright thanks. I think for the moment we'll leave this as is, and then other people can chime in if this is something they really want and then we can...

Any chance you saw this again @msuozzo?

Hey @msuozzo, Sorry for the silence, I just happened to come across something recently which sparked my inspiration about this. Looking at your PR https://github.com/google/oss-rebuild/pull/84, I see that it's a...

@msuozzo glad to hear it. I've left a note on the internal escalation with the findings so hopefully something can be done to avoid this in future. Sorry you were...

@ghthor sorry if you already responded but I couldn't spot your name in any of the existing threads. What about the current approach doesn't work for you on Linux? The...

`gh` tries to store the token in your keyring using https://github.com/zalando/go-keyring/blob/b38ab4b7224a1f2d243fc35cd3a646ad1cdcdf40/keyring_unix.go#L17 on linux. There's no blocker, requiring us to use this library. Feel free to file an issue on `cli/cli`...

Hey @Shion1305, thanks for creating this and sorry four your trouble. For forked repos we expect a default to be set so that we know whether to work with the...

Right, I can explain then. Since you didn't use `gh repo fork --clone`, or `gh repo clone`, `gh` is recognising that it is working on a fork because when working...

> About the current issue, do I have it right that the overall improvement being considered is the setting of the only remote (in the case of git clone clones)...

Also relevant issue that I came across today which was surprising behaviour to me: https://github.com/cli/cli/issues/9152