• Mr. Satan@monyet.cc
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    In my, rather short (5ish years profesionally), career I needed to rebase once. And it was due to some releasing fuck up, a branch had to be released earlier and hence needed to be rebased on another feature branch scheduled for release.

    Otherwise, fetch » pull » merge, all day, every day.

    • QuadriLiteral@programming.dev
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      I rebase almost daily. I (almost) never merge the main branch into a feature branch, always rebase. I don’t see the point of polluting the history with this commit (assuming I’m the only dev on this branch). I also almost always do an interactive rebase before actually pushing a branch for the first time, in order to clean up commits. I mostly recreate my commits from scratch before pushing, but even then I sometimes forget to include a change in a commit I’ve just made so I then do an interactive rebase to fold fixup commits into the commits they should’ve been in.

      I like merging for actually adding commits from a feature branch to main (or release or …)