Menu

Post image 1
Post image 2
1 / 2
0

Announcing gh-observer: Waiting for CI Should Not Be Misery

DEV Community·Christopher Hicks·18 days ago
#Ih9EmbVc
#github#cli#tui#observer#fullscreen#checks
Reading 0:00
15s threshold

Look, I know what you're thinking: "Another dev scratched their own itch and now they want to tell me about it." Guilty. But hear me out, because this particular itch has probably been annoying you too, and the scratch is genuinely useful. The Problem Nobody Talks About Here's the scenario that broke me: I push a PR, immediately run gh pr checks --watch , and... it bombs out with an error because GitHub Actions hasn't queued anything yet. So I wait. I run it again. Maybe it works, maybe it doesn't. And when it finally does start showing me checks, I'm staring at a list of job names with no idea whether that 3m 52s I've been waiting is normal or a sign that something's silently wedged. The standard gh pr checks --watch has had some real gaps for a while now: It doesn't handle startup delay. GitHub Actions typically takes 30-900 seconds to queue jobs after a PR is created or pushed to. The built-in watcher just... gives up during that window. No queue latency visibility.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More