• Elvith Ma'for@feddit.org
    link
    fedilink
    arrow-up
    13
    ·
    8 hours ago

    That’s basically my commit history for every repo where I need the pipeline to run to see if everything works.

    • ranzispa@mander.xyz
      link
      fedilink
      arrow-up
      1
      ·
      4 hours ago

      When I do that I always have a Dev branch that I use as the production branch to run the actual calculations.

      When I get something working I merge it off, clean up the history a little bit, rebase main onto it and then rebase de onto main.

    • kungen@feddit.nu
      link
      fedilink
      arrow-up
      4
      ·
      7 hours ago

      Haha same. But that’s why you do it in another branch, and then squash-merge.

      • ranzispa@mander.xyz
        link
        fedilink
        arrow-up
        1
        ·
        4 hours ago

        I like squash merge on small changes, but when larger code changes are there it becomes a huge commit which is difficult to review if you ever have to go back.

        • psycotica0@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          4 hours ago

          Right… for sure… but then if you don’t want to squash, then it doesn’t matter you can’t squash a merge commit.