Reading CI logs without losing the story you wanted to tell

Start from the failing job name, not the first red line. Most platforms group steps; the failing step usually contains the command that matters.

Copy the smallest failing snippet into your notes before you re-run anything. Re-runs are useful, but they scroll the evidence away.

Translate the error into human language before you comment publicly. "Type mismatch on line 48" reads calmer than pasting two hundred lines without a highlight.

If the failure is flaky, say so and link prior occurrences. Maintainers appreciate honesty about nondeterminism more than silent retries.

Close the loop when you push a fix. A short "pushed, waiting for CI" note prevents someone else from picking up the same task.