Dany nes...@gmail.com writes:
Again, I think the case where one intends to force push many branches
is certainly not as common as the case where one intends to force push
one branch, so why does git's default behavior leave the user in the
position of fscking himself over pretty badly?
I
Hi,
I had a pretty sucky thing happen to me today: while remote tracking a
non-master branch, I force pushed. This had the intended effect of force
pushing the branch I was working on, but also the unintended function of force
pushing all branches I wasn't on.
I'm open to anyone's thoughts
Hi Dany,
Dany wrote:
I had a pretty sucky thing happen to me today: while remote tracking
a non-master branch, I force pushed. This had the intended effect of
force pushing the branch I was working on, but also the unintended
function of force pushing all branches I wasn't on.
Yeah, I agree
3 matches
Mail list logo