3 ms·
...why? Isn't this exactly what rebase is for? Just plain, boring, non-interactive rebase.
by singpolyma3 2y ago
...why? Isn't this exactly what rebase is for? Just plain, boring, non-interactive rebase.
- recursive 2y agoMaybe? But it's also what merge is for. If I used rebase like this regularly it would become difficult to determine if a given commit is an ancestor of HEAD. Sometimes I like to do that.
- klysm 2y agoYes this is exactly what rebase is for, but a lot of developers do the merge based workflow.