miniblog.

← Back to all posts
Apr 13, 2021 at 05:22
1
It's not easy to display a log file nicely in a browser. The file might be huge. Users expect to be able to link to lines. It might have colour or control codes. I've been pretty impressed with the GitHub actions UI, compared with other CI tools.
How GitHub Actions renders large-scale logs
How GitHub Actions renders large-scale logs
Rendering logs in a web UI might seem simple: they are just lines of plain text. However, there are a lot of additional features that make them more useful to our users.

Related Posts

Apr 22, 2026 at 19:20
1
AI agents (OpenClaw, Hermes Agent etc) seem to be increasingly standardising their design. You have a UI for the markdown files writable by the agent (sometimes just Obsidian) plus a set of CLI tools for performing actions. I've seen so many new CLIs recently too.
Sep 26, 2023 at 21:32
TIL about actionlint, a static analysis tool for GitHub action YAML files: https://github.com/rhysd/actionlint Seems really useful, developing actions can be tricky.
GitHub - rhysd/actionlint: :octocat: Static checker for GitHub Actions workflow files
GitHub - rhysd/actionlint: :octocat: Static checker for GitHub Actions workflow files
:octocat: Static checker for GitHub Actions workflow files - rhysd/actionlint
Sep 4, 2023 at 23:26
Ooh, I've just discovered that you can enable actions on GitHub pull requests by default! This is the actions settings page. My understanding is that GitHub introduced these limits to prevent people trying to run cryptominers on GitHub actions. Sounds like GitHub has largely fixed it.
Photo