docs/private-fork-flow.md
Use this as the default AI-safe procedure when work must be pushed to a private fork, not public origin.
f sync --push and commit flows consistently target the private remote.cd <repo-dir>
git remote add <private-remote> [email protected]:<your-user>/<repo>-i.git
git fetch <private-remote>
flow.toml.[git]
remote = "<private-remote>"
git remote -v
Expected pattern:
origin and/or upstream are read/sync sources.<private-remote> is writable push target.cd <repo-dir>
git status --short --branch
git diff --stat
git diff
f commit --slow --review-model codex-high
f sync --push
Flow behavior:
f sync --push uses [git].remote when configured.[git].remote, then legacy [jj].remote, then origin.Use this exact phrase when you want review-first behavior:
analyze diff commit and push
Expected assistant behavior:
git status --short --branch, git diff --stat, git diff.f commit --slow --review-model codex-high.f sync --push.[git].remote or fallback origin).git status --short --branch and git diff --stat.flow.toml [git].remote plus git remote -v.git config --get branch.$(git rev-parse --abbrev-ref HEAD).remote || true
git remote get-url <private-remote>
Then run:
f sync --push
docs/commands/sync.mddocs/flow-toml-spec.mddocs/private-mirror-sync-workflow.mddocs/commands/upstream.md