• RecluseRamble@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    10 months ago

    Just remember to not combine it with force push or you’re in for some chaos (rewriting history team members have already fetched is a big no-no).

      • expr@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        10 months ago

        Or, you know, on your own feature branch to clean up your own commits. It’s much, much better than constantly littering your Branch’s history with useless merge commits from upstream, and it lets you craft a high-quality, logical commit history.

        • RecluseRamble@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          10 months ago

          Of course it has its uses. I didn’t mention them because the guy just learned about rebase - it’s unlikely to be applied flawlessly from the start.

      • zalgotext@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Force pushes are perfectly safe if you’re working on your own branch, and even if you’re sharing a branch, you can still force push to it as long as you inform and coordinate with whoever else is working on that branch.