Andy Feller

@samcoe @williammartin : after talking with one of our beloved Actions hubbers, I don't think there are any security or product concerns if we wanted to add a flag that...

> I am not opposed, but I think it would be nice if this was directly supported by the API instead of us having the find each selected repository ourselves....

With @yvele touching on this in #9383, I'm going to re-engage internally to see what might be done at the API layer to provide relief for this issue as doing...

Thank you for opening this issue, @AaronMoat! 🙇 Through initial triaging, I think all of this goes back to https://github.com/cli/cli/pull/704 and how we're determining the tracking branch. ### Walking through...

@AaronMoat : I think the issue here lies in the additional arguments you're using to clone the repository, which prevents your local repository of pulling remote references needed to detect...

@AaronMoat : With everything above, I don't know if this is really a bug in `gh` as I don't think there's any other way to detect local/remote branch situations. That...

> I have been using this for a clone, modify, pr flow for some automated batch changes - so for larger repositories it's quite inefficient to do a full clone....

@wingleung : open to revisiting this with @williammartin given that all the former GitHub CLI maintainers involved have left GitHub and moved onto other pursuits. ### Where is the actual...

> another alternative could be to get the remote from the current branch > > ➜ git rev-parse --abbrev-ref --symbolic-full-name @{u} > origin/add-remote-check-to-secret-and-variable > ☝️ we now know the local...

@arunsathiya : Thank you for raising this issue up and your diligent efforts to uncover the problem! 🤗 It seems like the following block of code is at the heart...