• IanTwenty@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        4 days ago

        I know. The author suggests:

        Experiment with new-to-you version control systems like Fossil, Mercurial, and Pijul.

        The author is:

        learning about different version control systems. For example, the differences between Fossil and git revealed a lot of my biases towards git simply because it’s familiar (and Fossil seems really cool). Reading about the theory behind Pijul absolutely bends my brain into knots. I keep trying anyway because conflicts in git are frustrating and I’d like a better solution.

        The author says:

        It would be nice to move beyond git one day and have a better experience for managing complex codebases, and not on GitHub’s timeline.

    • KissYagni@programming.dev
      link
      fedilink
      arrow-up
      4
      ·
      4 days ago

      I gave a try to jj. It’s fine for personal projects or small team and make the workflow a bit easier. No more “git add; git commit; git push” each time you do a modification. You just “jj git push” and everything will be automatically pushed.

      However, the biggest criticism I have is that he doesn’t encourage to push every time. It really encourages you to keep your modif locally and push only to create a PR, and that’s not a good approach.

      Even if you code is WIP, even if everything crash, you really should push your code to backup it. Who cares ? As long as it is not on master branch, it’s your own mess.