better errors for `gh` when not logged in

[amtoine]

right now, the error is not that great when running gh ... being logged out 🤔
and it does not fail in the sense that the LAST_EXIT_CODE is not set to 1 in that case 🤔

an idea that looks to be working: add gh auth status at the start

remaining things: what happens when the user is

• logged out: fails with You are not logged into any GitHub hosts. Run gh auth login to authenticate.
  • FEATURE: add check-gh-logged-in before running gh #20
• logged in: ??? => --logged-out option to query the API with http get

[melMass]

right now, the error is not that great when running gh ... being logged out 🤔 and it does not fail in the sense that the LAST_EXIT_CODE is not set to 1 in that case 🤔

Ah, rrrhh so many are not following proper exit codes, your option sound like a good one although the command isn't the fastest (at least when logged)

• logged out: fails with You are not logged into any GitHub hosts. Run gh auth login to authenticate.

I would output the same error verbatim, probably prefix with some "Host Error" or something similar

• logged in: ??? => --logged-out option to query the API with http get

I'm not familiar with this flow can you elaborate?

[amtoine]

Ah, rrrhh so many are not following proper exit codes, your option sound like a good one although the command isn't the fastest (at least when logged)

yeah, gh auth status takes a bit of time, it's true 🤔
it's the only thing i've found so far 😕

I would output the same error verbatim, probably prefix with some "Host Error" or something similar

👍

I'm not familiar with this flow can you elaborate?

instead of using gh, you call poll the REST API of GitHub directly 😏
see this gist for instance 😋