Let's Make Sure Github Doesn't Become the only Option - Edward Loveall
-
This post did not contain any content.
-
This post did not contain any content.
Jujutsu is another git alternative I keep seeing around and came to mind reading this:
https://steveklabnik.github.io/jujutsu-tutorial/introduction/what-is-jj-and-why-should-i-care.html
-
Jujutsu is another git alternative I keep seeing around and came to mind reading this:
https://steveklabnik.github.io/jujutsu-tutorial/introduction/what-is-jj-and-why-should-i-care.html
Why? This is isn't about git. It's about github. Two completely different tools.
-
This post did not contain any content.
Codeberg has a git "ci" possibility (woodpecker?). What is missing?
-
This post did not contain any content.
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.
-
This post did not contain any content.
Love codeberg for personal, already move our business to gitlab
-
This post did not contain any content.
I just set up a private forgejo instance and it was really quick and easy. So far I'm enjoying it.
-
Why? This is isn't about git. It's about github. Two completely different tools.
I think it’s valid unless one thinks git should be the only standard. Looking at other tool chains opens options
-
I think it’s valid unless one thinks git should be the only standard. Looking at other tool chains opens options
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.
-
I just set up a private forgejo instance and it was really quick and easy. So far I'm enjoying it.
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.
-
Why? This is isn't about git. It's about github. Two completely different tools.
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.
-
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.
Jujutsu isn't supposed to be just a git frontend actually
-
Jujutsu is another git alternative I keep seeing around and came to mind reading this:
https://steveklabnik.github.io/jujutsu-tutorial/introduction/what-is-jj-and-why-should-i-care.html
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.
-
This post did not contain any content.
I have a Forgejo instance with all my private repositories and use GitHub for my public repositories I want to share with others / collaborate on. I'm planning to switch to Forgejo / Codeberg for my public repositories when Forgefed has been implemented.
-
Codeberg has a git "ci" possibility (woodpecker?). What is missing?
wrote last edited by [email protected]People. Most people are still on GitHub and don't see things on Codeberg / GitLab nor are they willing to create an account. It's a classic case of the network effect.
-
Codeberg has a git "ci" possibility (woodpecker?). What is missing?
Not all actions run on it.
Also, GitHub infrastructure is free and really performance, that's why I use it even if I have my own for server.
Also, discoverability. For the projects that I want to show to the world, GitHub is best, since it's most likely people see it there.
-
This post did not contain any content.
Gitea is awesome and fairly easy to get up and running.
-
Not all actions run on it.
Also, GitHub infrastructure is free and really performance, that's why I use it even if I have my own for server.
Also, discoverability. For the projects that I want to show to the world, GitHub is best, since it's most likely people see it there.
Free like in Microsoft free...
For the discoverability I totally understand, but it's a behemoth, it should be split up IMO.
On a side note, I have never had any performance problems with Codeberg, but my projects aren't that big.
