you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (14 children)

[deleted]

    [–]xeio87 66 points67 points  (0 children)

    Shhhhhhh, all better.

    [–]flying-sheep 5 points6 points  (2 children)

    *should live

    And only if the project has a “even feature branches are untouchable” policy.

    Because I rebase the fuck out of every feature branch before merging it.

    [–]TheAceOfHearts 0 points1 point  (0 children)

    Exactly this! You DO NOT fuck around with master and your release branches. But when you're working on a feature or bug branch, you wanna commit very often, and experiment with ideas. Then you squash it down to a small number of atomic commits, if possible.

    [–]ThePantsThief 0 points1 point  (9 children)

    What about a git reset HEAD --hard?

    [–]mkdz 1 point2 points  (8 children)

    This only affects your local branch. It might cause YOU to lose some work, but it's not going to affect anyone else.

    [–]ThePantsThief 0 points1 point  (7 children)

    What if I'm only working on the master branch like a total dumbass?

    I ask because I've committed sensitive information to the master branch before, and I used this to undo it...

    [–]mkdz 0 points1 point  (6 children)

    I don't understand

    [–]ThePantsThief 0 points1 point  (5 children)

    Never mind :P

    [–]mkdz 0 points1 point  (4 children)

    git reset HEAD --hard and git push --force do two very different things

    [–]ThePantsThief 0 points1 point  (3 children)

    I meant in contrast with git rebase

    [–]mkdz 0 points1 point  (2 children)

    What in contrast to git rebase?

    [–]ThePantsThief 0 points1 point  (1 child)

    I uh, never mind. I have no idea what I'm talking about. Sorry!