The best way to control Claude Code, Codex and more from any computer or phone
Mirrored from https://github.com/Camo67/t3code.git
Synced Nov 22, 15:45 UTC
docs: read GitHub Actions logs through cafe (#25343)
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Julius Marminge committed
Oct 25, 2026 at 23:09 UTC
4e493b1492c295475e5c4d1b971677b1bd305960
2 files changed
+9
-9
AGENTS.md
+1
-1
@@ -139,7 +139,7 @@ For authorized mobile verification, a missing or outdated native client is an in
139
## Pull requests
140
141
- Never make a PR unless the developer explicitly asks you to do so.
142
-- If `origin` is git.cafe, follow [GitCafe mirror](docs/operations/development.md#gitcafe-mirror-optional): push to `origin`, open and track PRs with `cafe` and their git.cafe URLs, and keep `gh` for CI logs and merging.
142
+- If `origin` is git.cafe, follow [GitCafe mirror](docs/operations/development.md#gitcafe-mirror-optional): push to `origin`, open and track PRs with `cafe` and their git.cafe URLs, and keep `gh` for merging.
143
- Conventional commit titles, plain language: `fix(web): new threads no longer spike CPU`.
144
- Body: the problem in a sentence or two, then how you fixed it. End with the model and harness that did the work.
145
- UI changes need before/after images. Motion or timing needs a short video.
docs/operations/development.md
+8
-8
@@ -28,8 +28,8 @@ GitCafe.
28
```sh
29
git remote set-url origin https://git.cafe/pingdotgg/t3code.git
30
git remote add github https://github.com/pingdotgg/t3code.git
31
-gh repo set-default pingdotgg/t3code # for the few `gh` commands below
32
-bun install -g @gitcafe/cli # `cafe` needs Bun 1.2 or newer
31
+gh repo set-default pingdotgg/t3code # `gh` is still used for merging
32
+bun install -g @gitcafe/cli@latest # `cafe` needs Bun 1.2 or newer
33
cafe auth login && cafe auth http setup
34
cafe skills install --global # optional: cafe-* skills for coding agents
35
```
@@ -39,14 +39,14 @@ With `origin` on git.cafe, work through GitCafe and leave GitHub's API alone:
39
- Push to `origin`, open PRs with `cafe pr create` (`--head owner/repo:branch` from a fork) or
40
`cafe stack submit`, and use `cafe` for everything after that. Link the git.cafe PR URL, not the
41
github.com one, wherever a tool tracks the PR, so polling stays on GitCafe.
42
-- Read checks with `cafe pr status <n>`.
42
+- Read checks with `cafe pr status <n>`, and GitHub Actions logs with `cafe ci logs <run>` (run ids
43
+ from `cafe ci list --pr <n>`). `cafe ci rerun <run>` reruns one. These need `cafe` 0.11 or newer.
44
- Write closing references as `Fixes pingdotgg/t3code#<n>`. GitCafe turns a bare `#<n>` in text it
45
syncs to GitHub into a git.cafe link, and GitHub does not close issues from those.
45
-- Two things still need `gh`: CI logs and reruns (`gh run view --log`, `gh run rerun`), and
46
- merging, with `gh pr merge <n> --match-head-commit <sha>`, because `cafe pr merge` cannot pin
47
- the commit you reviewed.
48
-- `cafe` flags differ from `gh`: `--repo` not `-R`, `cafe issue comments <n>` not `--comments`,
49
- `cafe pr status` not `pr checks`. `cafe api` paths omit `/api` (`cafe api /repos/...`).
46
+- Merge with `gh pr merge <n> --match-head-commit <sha>`, because `cafe pr merge` cannot pin the
47
+ commit you reviewed.
48
+- `cafe` commands differ from `gh`: `cafe issue comments <n>` not `--comments`, `cafe pr status`
49
+ not `pr checks`.
50
51
## Choosing a dev process
52