You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For reasons (mostly just being a long lived project afaik), there are a lot of commands that interact with the GitHub API directly via an http.Client rather than the api.Client (and associated go-ghapi.Client underneath). This hasn't really been an issue, but now does present a challenge in supporting behaviour that should cross all API requests.
We should pay down some of this debt by trying to consolidate all (may end up being limited to most) API interactions behind the api client (or a similar abstraction).
There are a series of commands that should hopefully be lift-and-shift, and some that will require some more rework no longer having access to the original raw http response.
Expected Output
All (or most) api interactions go through the api client.
A comment is left on this issue explaining any interactions that could not go through the same api client.
Suggesting the enhancement label here - this is a technical debt/refactoring task to consolidate API interactions behind a shared api.Client abstraction rather than scattered http.Client usage. It's not a bug (nothing is broken), but an improvement to enable cross-cutting API behaviour (as linked in #13717). No duplicate issues were found tracking this specific consolidation effort.
Activity
cli-triage commentedon Jul 28, 2026
Suggesting the
enhancementlabel here - this is a technical debt/refactoring task to consolidate API interactions behind a sharedapi.Clientabstraction rather than scatteredhttp.Clientusage. It's not a bug (nothing is broken), but an improvement to enable cross-cutting API behaviour (as linked in #13717). No duplicate issues were found tracking this specific consolidation effort.