fix(git): auto-accept commit message when continuing rebase

[boneskull]

Closes #49

[boneskull]

📚 Pull Request Stack

• branch: main
  • fix(git): auto-accept commit message when continuing rebase #71 - branch: issue-49 (this PR)

---

Managed by gh-stack

[claude]

Claude finished @boneskull's task in 1m 9s —— View job

---

Code Review

• Gather context
• Read changed file and diff
• Provide review feedback

---

Summary: This is a minimal, correct fix. The change is a single line in internal/git/git.go:290.

The change:

- return g.runInteractive("rebase", "--continue")
+ return g.runInteractive("-c", "core.editor=true", "rebase", "--continue")

This passes -c core.editor=true to git, setting the editor to the Unix true command (which exits immediately with code 0) for this single invocation only. When git rebase --continue needs to open an editor to confirm a commit message, it runs true instead — effectively auto-accepting the existing message without blocking.

Assessment: Correct and appropriate. The -c flag is the right mechanism here because it scopes the config override to a single invocation without modifying the user's git config.

---

Observations:

1. Windows compatibility — true is a POSIX command. On Windows, this works in practice because Git for Windows ships true in Git Bash, but it's a subtle assumption. No action needed unless Windows is an explicitly supported target.

2. No tests for RebaseContinue — There's no test coverage for this function (confirmed by searching *_test.go). This is understandable since testing interactive git rebase flows is difficult. Not a blocker.

3. Consistency with other rebase helpers — RebaseHere (git.go:381) and RebaseOntoHere (git.go:388) still use plain runInteractive("rebase", ...) without the editor override. If those ever encounter a commit message prompt, they'd block too. That said, initial rebase operations are less likely to hit this than --continue, so the targeted fix makes sense.

No issues blocking merge. The fix is minimal, safe, and solves a real UX problem in the gh stack continue flow.