Let's Make Sure Github Doesn't Become the only Option - Edward Loveall (blog.edwardloveall.com)
from mesamunefire@piefed.social to programming@programming.dev on 17 Sep 20:33
https://piefed.social/post/1274511

#programming

threaded - newest

IanTwenty@lemmy.world on 17 Sep 21:08 next collapse

Jujutsu is another git alternative I keep seeing around and came to mind reading this:

…github.io/…/what-is-jj-and-why-should-i-care.htm…

thenextguy@lemmy.world on 17 Sep 21:12 next collapse

Why? This is isn’t about git. It’s about github. Two completely different tools.

limer@lemmy.ml on 17 Sep 23:15 next collapse

I think it’s valid unless one thinks git should be the only standard. Looking at other tool chains opens options

Ephera@lemmy.ml on 18 Sep 02:56 collapse

Jujutsu is a Git frontend, from what I understand, much like there’s tons of Git GUIs. So, you interact with it in a different way, but you still push to a Git repository and others can interact with your code by using Git.

I guess, it somewhat lessens the grip of Git, because they can hook different backend services (e.g. Subversion, Mercurial, Fossil) into this frontend, and from what I understand, they plan to develop an own backend eventually. But yeah, for now, the communication standard is still Git.

[deleted] on 18 Sep 07:53 collapse
.
IanTwenty@lemmy.world on 18 Sep 06:47 collapse

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 on 18 Sep 08:18 collapse

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.

Valmond@lemmy.world on 17 Sep 21:16 next collapse

Codeberg has a git “ci” possibility (woodpecker?). What is missing?

goodboyjojo@lemmy.world on 17 Sep 21:35 next collapse

I agree we need more diverse options to host source code projects with. I remember when people moved their source code to other places like gitlab when github was bought by microsoft.

Cyberflunk@lemmy.world on 17 Sep 22:29 next collapse

Love codeberg for personal, already move our business to gitlab

jeena@piefed.jeena.net on 17 Sep 22:59 next collapse

I already set up my own forgejo instance and moved my code off of GitHub:

https://git.jeena.net

yimyam@piefed.social on 17 Sep 22:58 collapse

I just set up a private forgejo instance and it was really quick and easy. So far I'm enjoying it.

addie@feddit.uk on 18 Sep 06:37 collapse

Yeah. Got a raspberry pi sat by our router, being the home dns server and fileshare. Installing forgejo was a one-liner, configuring nginx to serve it over https took about half a dozen. Very easy, perfectly reliable.