[shalk]

git commit on an initial commit under a Chinese locale outputs:
[master（根提交） fb597ec] Initial commit

The old code found the first space and sliced line[1..hash_start], yielding "master（根提交）" (21 bytes). hash.len() >= 7 was true, so it tried &hash[..7] — but byte 7 falls inside the 3-byte '（' character, causing a panic.

Two bugs were present:

1. Logic: the code grabbed the token before the first space (branch name), not the commit hash. The hash is always the last whitespace-separated token inside the [...] brackets.
2. Safety: raw byte slicing on a potentially non-ASCII string.

Fix: find ']', extract the bracket content, split_whitespace() and take next_back() to get the hash. Use chars().take(7) for the short-hash slice so it is always char-boundary-safe.

Summary

Test plan

• cargo fmt --all && cargo clippy --all-targets && cargo test
• Manual testing: rtk <command> output inspected

Important: All PRs must target the develop branch (not master).
See CONTRIBUTING.md for details.

[pszymkowiak]

[w] wshm · Automated triage by AI

📊 Automated PR Analysis

🐛 Type	bug-fix
🟢 Risk	low

Summary

Fixes a panic caused by slicing into multibyte UTF-8 characters when parsing git commit output under non-ASCII locales (e.g., Chinese). The fix correctly extracts the commit hash as the last token within brackets and uses char-safe slicing instead of raw byte indexing.

Review Checklist

• Tests present
• Breaking change
• Docs updated

---

Analyzed automatically by wshm · This is an automated analysis, not a human review.

[CLAassistant]

All committers have signed the CLA.

[aeppling]

Hey @shalk , thanks for the fix and sorry for the delay

This look good to me