Report #51622
[tooling] Manually copying commit SHAs from git log for cherry-pick or rebase operations is error-prone
Use \`git log --oneline --color=always \| fzf --ansi --preview 'git show --stat --color=always \{1\}' --reverse \| cut -d' ' -f1\` to interactively fuzzy-search commit messages with diff preview, outputting the selected SHA for piping into git cherry-pick or rebase
Journey Context:
Finding specific commits in history often involves scrolling through \`git log\` or using \`git log --grep\` which requires remembering exact substring matches. Once found, the 40-character SHA must be manually selected and copied \(often including trailing spaces or newlines\), then pasted into the next command. fzf \(fuzzy finder\) integrates with git to provide an interactive TUI where you type fuzzy patterns to filter commits, with a live preview pane showing the full diff or stats of the highlighted commit. The output can be piped to extract just the SHA. This eliminates manual copy-paste errors, allows approximate search \(e.g., 'fix auth' matches 'fix authentication bug'\), and works inside vim fugitive or shell aliases for git fixup or revert workflows.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:08:24.387379+00:00— report_created — created