rtk-ai/rtk

rtk git commit hides post-commit hook output

Open

#1,355 建立於 2026年4月17日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Rust (48,085 star) (2,914 fork)batch import
bugeffort-smallfilter-qualitygood first issue

描述

When running git commit through rtk, output produced by a Git post-commit hook is not shown.

Minimal reproduction:

tmp=$(mktemp -d)
cd "$tmp"

git init -q
git config user.email test@example.com
git config user.name Tester

mkdir -p .git/hooks
cat > .git/hooks/post-commit <<'EOF'
#!/bin/sh
echo HOOK_STDOUT_visible
echo HOOK_STDERR_visible >&2
EOF
chmod +x .git/hooks/post-commit

printf "one\n" > f.txt
git add f.txt
git commit -m native

printf "two\n" >> f.txt
git add f.txt
rtk git commit -m rtk

Expected behavior:

rtk git commit should show the output produced by the post-commit hook, similar to native git commit.

Native git commit output includes:

HOOK_STDOUT_visible
HOOK_STDERR_visible
[main ...] native

Actual behavior:

rtk git commit only prints the compact success output:

ok

The hook output is not visible. This makes hook-generated messages easy to miss, including post-commit notices, validation summaries, local workflow hints, or follow-up instructions.

貢獻者指南

技術棧
rust
領域
cli
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic Rust knowledgeunderstanding of git hooks
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Inspect how rtk executes git commands, specifically the subprocess handling in the git module. Look for where stdout/stderr of subprocesses is captured or piped. The issue is that post commit hook output is lost, likely because rtk only captures the final commit output. Check if there is any buffering or filtering of subprocess output. The fix may involve ensuring all subprocess output is forwarded to the user without being suppressed.
rtk git commit hides post-commit hook output · rtk-ai/rtk#1355 | Good First Issue