Running CI weekly on dotfiles setup.sh inside a fresh Ubuntu container to catch breakage
4310sy · x · 2026-10-24
Developer ShisatoYano added GitHub Actions CI to verify his dotfiles setup.sh actually works on a bare machine.
Key points:
- Runs setup.sh in a clean ubuntu:24.04 container as a regular user with passwordless sudo, since the host runner's preinstalled gh/go/node/docker would hide missing installs
- Idempotency check: second run must report changed=0 after a first failed=0 run
- Smoke test verifies all installed commands are present
- Triggers: push/PR on relevant paths, a weekly Monday 6:00 JST schedule (many tools pull upstream latest, so scheduled runs catch upstream breakage), and manual runs
The clean-container run also surfaced a real bug: tabctl install detects browsers via /.config/google-chrome, which doesn't exist until Chrome's first launch (Chrome isn't playbook-managed), failing the install and skipping later tasks. Fixed by skipping registration when the directory is absent, with a debug message prompting a re-run.
The PR was generated with Claude Code.
More from coding & agent
- Codex Computer Use fails to capture Safari on Mac mini M4 with SCStreamErrorDomain -3811/-3812 — darkprinceimmortal · 2026-10-24
- Mubit trains small models from your own agent API traffic to cut cost and latency — rohanpaul_ai · 2026-10-24
- Heavy AI user: marketed automations are fragile, exhausting, and dumber than we admit — mrks86 · 2026-10-24
- Google's playbook: evaluating AI agents beyond the vibe check — bibryam · 2026-10-24
- Codex CLI's hidden remote-control feature praised as better than Claude Code's — antirez · 2026-10-24
- PWAs can't use foldable screens on the Duo yet, but two Chrome flags unlock the APIs — mitsuhiko · 2026-10-24