jesseduffield / jesseduffield/lazygit
Don't use an interactive rebase when rebasing onto another branch
Open
enhancement
- Dominant language
- Go
- Stars
- 82.4k
- Forks
- 3k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 19
Description
**Is your feature request related to a problem? Please describe.**
Currently we always interactive rebase when rebasing onto another branch. This is not obvious behaviour and causes surprising behaviour (as we saw in https://github.com/jesseduffield/lazygit/pull/2429).
**Describe the solution you'd like**
We should not pass --interactive when rebasing onto a branch, BUT we should _still_ show the commits that are yet to come in the rebase, because the visual aid is handy.
Contributor guide
Assessment
This issue has not been assessed yet.