Summary

On March 9, 2026, retesting the latest installed local binary /home/pavelbe/bin/rtk (rtk 0.27.2) showed that rtk git status outside a Git repository returns exit 0 instead of matching Git exit code.

This appears to be a separate bug from #163.

Repro 1: current directory outside a repo

cd /tmp

git status; echo $?
# fatal: not a git repository (or any of the parent directories): .git
# 128

rtk git status; echo $?
# Not a git repository
# 0

Repro 2: explicit -C <path> outside a repo

git -C /tmp status; echo $?
# fatal: not a git repository (or any of the parent directories): .git
# 128

rtk git -C /tmp status; echo $?
# Not a git repository
# 0

Expected

rtk git ... status should preserve Git failure semantics for non-repo status:

• non-zero exit code (128 here),
• error reported on stderr,
• no successful-looking exit 0.

Actual

rtk git ... status prints Not a git repository and exits with 0.

Notes

• The original rtk git -C <path> parser rejection from bug: rtk git -C <path> ... is rejected (works only via separator form) #163 appears fixed on 0.27.2.
• This report is only about the remaining exit-code / stdout-vs-stderr parity mismatch for non-repo status.