Put your CI build status in your tmux status bar. Know immediately when something breaks.
C:✓ B:✓ D:✓ V:✓ │ 14:32 01-Feb
When you're doing trunk-based development, you need to know immediately when CI fails. Not 10 minutes later when you context-switch. Not at the end of the day.
The best gate is one you can't forget to check. When it's in your peripheral vision all day, you're not going to forget.
| Script | Platform | Requires |
|---|---|---|
ci-status-github.sh |
GitHub Actions | gh CLI |
ci-status-gitea.sh |
Gitea Actions | teax |
# GitHub users
curl -o ~/.local/bin/ci-status.sh \
https://gist.githubusercontent.com/.../ci-status-github.sh
chmod +x ~/.local/bin/ci-status.sh
# Gitea users
curl -o ~/.local/bin/ci-status.sh \
https://gist.githubusercontent.com/.../ci-status-gitea.sh
chmod +x ~/.local/bin/ci-status.shEdit the script and set your repo:
REPO="owner/repo"For Gitea with self-signed certs, uncomment:
export TEAX_INSECURE=1In your .tmux.conf or session script:
# Simple - just CI status
set -g status-right '#(~/.local/bin/ci-status.sh) │ %H:%M'
# With refresh interval (default is 15s, this sets 30s)
set -g status-interval 30For multiple projects, put the script in each project and reference it:
# In your tmux session setup
set -g status-right '#($PROJECT_DIR/scripts/ci-status.sh) │ %H:%M'| Output | Meaning |
|---|---|
CI:✓ |
All workflows passed |
CI:✗ |
Something failed |
CI:⏳ |
Running |
CI:- |
No runs found for this commit |
CI:? |
Error (not in repo, API issue, etc.) |
+3 |
3 unpushed commits (showing remote CI status) |
The Gitea script shows individual workflow status:
C:✓ B:✓ D:✓ V:✓
Where:
C= ci.yml (lint, test)B= build.ymlD= staging-deploy.ymlV= staging-verify.yml
Customize the WORKFLOWS variable to match your pipeline.
When your local branch is ahead of remote, the scripts show what CI actually ran (remote HEAD) plus how many commits you haven't pushed:
CI:✓ +3
This means: "CI passed for what's on the server, but you have 3 local commits not yet pushed."
- teax - CLI for Gitea Actions (fills gaps in
tea) - gh CLI - GitHub's official CLI
- Blog post: Solo Dev Release Process - Why CI visibility matters
MIT