feat: show a running job's steps instead of a terminal #35
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/step-list"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Checklist
Problem
gh run watchtakes a run id and has no per-job flag, so<CR>onlintcwatched all thirty-nine checks. And a terminal running a redraw-in-place
program truncates to the window width and cannot be scrolled — both reasons we
had already disqualified terminal buffers for the log.
Solution
A running job renders its own steps:
This costs no new request.
M.renderalready callsgh.job, which alreadyreturns
steps[]— we were fetching them and discarding them when the log404'd. It is a normal
ci://buffer, so it scrolls, keeps the winbar,-,g?, and it becomes the log on the next poll after the job finishes.The steps are also written to
b:ci.checks, which is what the list poll from#34 looks at, so a job buffer refreshes on the same ten-second timer with no
new machinery.
Removed
The terminal shim, and with it the
b:ciwe were putting on a terminal bufferand the
-map on it.plugin/ci.luais untouched.Note
CheckRun.stepsdoes exist in GraphQL — I had it recorded as REST-only,which was wrong, and an introspection query shows
stepsright there among itsfields. It is not needed here, since adding
steps(first:40)to the list querywould return roughly 1,560 step nodes per poll for a 39-check pull request in
order to serve the one job you opened. The REST job request we already make is
both smaller and already in the code path.