Download workflow logs

Download workflow logs in GitHub — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need the full logs from the failed workflow that ran on main yesterday at 16:12. Download the…
I need the full logs from the failed workflow that ran on main yesterday at 16:12. Download the workflow run artifacts and build logs, verify they include the step-by-step console output and the test-report files, and save them to my team's shared folder under devops/investigations/2026-07-16. Tell me if any expected files are missing before I escalate to QA.

Improve — make it easier to accept

+
Before I hand this to QA, make the download easy to review: put the failing test summary and the…
Before I hand this to QA, make the download easy to review: put the failing test summary and the top 200 lines of the build output first, then group the remaining step logs by job, and flag any steps that returned nonzero exit codes or timeout messages. Highlight where the last successful run differs in duration or exit code.

Decide — diagnose the stuck moment

+
The workflow on main failed during dependency restore at 16:12; I’m the engineer on call and the…

The CI run failed on a dependency restore step

The workflow on main failed during dependency restore at 16:12; I’m the engineer on call and the failure output shows a checksum mismatch for a vendored package. I don’t know if the cache is corrupted, a package was pushed upstream, or our lockfile is wrong. Who should I notify, what quick checks rule out local cache corruption, and what’s the safest next action to restore the pipeline without hiding the root cause?

Become — change the pattern

+
Over the last quarter our team wastes half a day per week chasing failed workflow runs that look…

We keep chasing flaky workflow failures and re-downloading logs

Over the last quarter our team wastes half a day per week chasing failed workflow runs that look identical: dependency restore or cache checksum errors, long downloads, and transient timeouts. Where are we most likely leaking time or credibility, and what three habits should we change so failures are reproducible, triageable, and avoidable—practical steps I can enforce this sprint?

Next to this one

Other code hosting work people do in GitHub.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.