Skip to content

Commit 6b292d9

Browse files
docs: drop the GitCafe mirror runbook for a generic forge mirror (#35773)
Co-authored-by: Claude Opus 5.5 <[email protected]>
1 parent 62647f4 commit 6b292d9

2 files changed

Lines changed: 10 additions & 27 deletions

File tree

‎AGENTS.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ For mobile verification, a missing or outdated native client is an install step,
149149
## Pull requests
150150

151151
- Never make a PR unless the developer explicitly asks you to do so.
152-
- 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.
152+
- `origin` is not always GitHub. Check `git remote get-url origin` before your first forge command and use that forge's CLI and skill. See [Forge mirror](docs/operations/development.md#forge-mirror-optional).
153153
- Conventional commit titles, plain language: `fix(web): new threads no longer spike CPU`.
154154
- Body: the problem in a sentence or two, then how you fixed it. End with the model and harness that did the work.
155155
- UI changes need before/after images. Motion or timing needs a short video.

‎docs/operations/development.md‎

Lines changed: 9 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -27,38 +27,21 @@ a new browser.
2727

2828
Prefer a container? See [Dev container](../internals/devcontainer.md) for VS Code and Codespaces setup.
2929

30-
## GitCafe mirror (optional)
30+
## Forge mirror (optional)
3131

32-
GitHub is the source of truth. [git.cafe/pingdotgg/t3code](https://git.cafe/pingdotgg/t3code) is a
33-
two-way synced mirror with much higher API rate limits, which helps when many agents work at once.
34-
You never need it to contribute.
35-
36-
Pushes, PRs, comments, reviews, labels, and issue edits made on GitCafe sync to GitHub within
37-
about a minute, and PR and issue numbers match. CI runs on GitHub, and its checks show up on
38-
GitCafe.
32+
GitHub is the source of truth. [source.tanstack.com/@pingdotgg/t3code](https://source.tanstack.com/@pingdotgg/t3code)
33+
is a two-way synced mirror built for many agents working at once. You never need it to contribute.
3934

4035
```sh
41-
git remote set-url origin https://git.cafe/pingdotgg/t3code.git
36+
git remote set-url origin https://source.tanstack.com/@pingdotgg/t3code.git
4237
git remote add github https://github.com/pingdotgg/t3code.git
43-
gh repo set-default pingdotgg/t3code # `gh` is still used for merging
44-
bun install -g @gitcafe/cli@latest # `cafe` needs Bun 1.2 or newer
45-
cafe auth login && cafe auth http setup
46-
cafe skills install --global # optional: cafe-* skills for coding agents
38+
src auth login --web && src auth setup-git
4739
```
4840

49-
With `origin` on git.cafe, work through GitCafe and leave GitHub's API alone:
50-
51-
- Push to `origin`, open PRs with `cafe pr create` (`--head owner/repo:branch` from a fork) or
52-
`cafe stack submit`, and use `cafe` for everything after that. Link the git.cafe PR URL, not the
53-
github.com one, wherever a tool tracks the PR, so polling stays on GitCafe.
54-
- Read checks with `cafe pr status <n>`, and GitHub Actions logs with `cafe ci logs <run>` (run ids
55-
from `cafe ci list --pr <n>`). `cafe ci rerun <run>` reruns one. These need `cafe` 0.11 or newer.
56-
- Write closing references as `Fixes pingdotgg/t3code#<n>`. GitCafe turns a bare `#<n>` in text it
57-
syncs to GitHub into a git.cafe link, and GitHub does not close issues from those.
58-
- Merge with `gh pr merge <n> --match-head-commit <sha>`, because `cafe pr merge` cannot pin the
59-
commit you reviewed.
60-
- `cafe` commands differ from `gh`: `cafe issue comments <n>` not `--comments`, `cafe pr status`
61-
not `pr checks`.
41+
With `origin` on the mirror, use `src` (it takes `gh`'s commands and flags) and its `source` agent
42+
skill for PRs, issues, reviews, and CI, and leave GitHub's API alone. Pull requests into `main`
43+
merge on GitHub, so GitHub's required checks and reviews still apply. Numbers can differ between
44+
the two forges; in text that reaches GitHub, use the GitHub number.
6245

6346
## Choosing a dev process
6447

0 commit comments

Comments
 (0)