3 ms·
One of the many reasons not to rebase code that's been pushed already.
by jimktrains2 14y ago
One of the many reasons not to rebase code that's been pushed already.
- Davertron 14y agoAs far as I know there's only one reason not to rebase code that's been pushed. My point was that pushing constantly as a backup mechanism isn't an option if you intend to rebase frequently (unless you're the only developer on the project).
- X-Istence 14y agoI have a personal clone of whatever project I am working on, any branches that I publish can be changed at any time using a push -f.