4 ms·
That looks so wrong to me. It says everywhere in the docs "never rebase something that's been published" and it says so for a reason. The fact that git lets yo
by beagle3 13y ago
That looks so wrong to me. It says everywhere in the docs "never rebase something that's been published" and it says so for a reason.
The fact that git lets you shoot yourself in the foot doesn't mean you should, definitely not incorporate this into working procedures.
If it's a private feature branch, don't make it public (pushing would still back it up on the server, though you'd have to know the sha1 to fixed it). If it's public, don't rebase it.
- penguindev 13y ago> and it says so for a reason. And yet you don't know the reason. It's because others may have merged your work or be dependent on it. In my case, that doesn't happen, because it's a private branch. I'm the only developer, but other people can look at it for review.