| ▲ | jinushaun 6 hours ago |
| `git history reword` is great. Using `git rebase -i` just to fix a spelling error is overkill and doesn’t actually do what I want. |
|
| ▲ | jauntywundrkind 4 hours ago | parent [-] |
| Why doesn't it do what you what? I hate to be the worry wart, but I am worried folks are going to avoid `git rebase -i` even more now. It is such an excellent excellent UI in my opinion: it shows you the history of what is clearly, and let's you modify it as you please! |
| |
| ▲ | NekkoDroid 3 hours ago | parent [-] | | > Why doesn't it do what you what? If you have anything else branching/referencing a commit after the reword commit that isn't part of the branch you are rebasing you now have all those references still pointing to the old commit and need to go through every one of them to fix them. | | |
| ▲ | WorldMaker an hour ago | parent [-] | | Which is a reminder that maybe `--update-refs` should be the default for `git rebase -i`. It's great that it is now going to be the default for both `git replay` and `git history`, and I know why git is conservative in updating defaults, but at some point there's a benefit to updating the defaults. (I'd also argue that `-i` itself should have long been the default for `git rebase`. Also, while we are at it, probably `--autosquash` should be default.) |
|
|
