3 ms·
So you can get a semantic and useful history before submitting a patch/PR for review (or before merge). Doing hacky and messy WIP commits is totally fine. Just
by 3np 4y ago
So you can get a semantic and useful history before submitting a patch/PR for review (or before merge).
Doing hacky and messy WIP commits is totally fine. Just clean them up before having others read them.
In case you're not aware:
git rebase --interactive [remote/]ref