5 ms·
If you rebase a lot, then you want to avoid pushing code constantly until you get it where you want it.
by Davertron 14y ago
If you rebase a lot, then you want to avoid pushing code constantly until you get it where you want it.
- jimktrains2 14y agoOne 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.
- deleted 14y ago[deleted]
- nathan_long 14y agoDepends on your team. I'm on a small one, and I often rebase and force push a branch I'm working on, because I know nobody else is working on it.
- philsnow 14y agoSo push to a remote feature branch that is named after your username, then rebase the changes in that feature branch onto the 'trunk' branch and push the result ? The D in DVCS is all well and good, but there are business reasons for having a canonical store of all source materials.