Your favorite search engine or LLM will show you in a second, it's really easy.
The problem is that it's not enough. The fact that Github uses Git specifically is a technical detail; it could use mercurial equally easily, as Bitbucket used to. Github Actions, OWNERS files, PRs and review tools, issue tracker, wiki are all not Git features.
Not a chance. I think you need to spend some time in low ball corporate IT. It's just monkeys throwing faeces at the wall. We only just levered them off subversion...
(I use Fossil 100% offline for personal projects for ref)
Not really. I've been around a while. Git for about 15 years. Subversion before that. Perforce before that. rcs before that (back down to sun3 machines). Mostly Fossil now for personal things.
What I am saying is that people learn as much as they need to. They generally don't need to know any more git than is required to interact with github. If anything problematic comes up, they go in with a wrecking ball because they don't truly understand what they are doing. And git has a lot of wrecking balls available.
If you threw them at raw git and asked them to collaborate with someone they'd be up shit creek. They have no idea how SSH or email works for example.
I mean, there are solutions, but none of them seems to have a large enough mindshare and efficiency. (Even though Github's code review tools are pretty spartan.)
They can be. A PR can be made and code review conducted by submitting a patch to a mailing list. That's how the kernel and, I think, git itself is developed.
CI/CD is really a methodology. It just means integrating/deploying stuff as soon as its ready. So you just need maintainers to be able to run the test suite and deploy, which seems like a really basic thing.
True, workers can still commit to their local git.
I've been looking into having a separate git server that we can commit to and add plain ole git hooks to, and just having it be synced with github as a clone.
I'd rather recommend Forgejo (a fork of Gitea developed under the auspices of Codeberg e.V.) instead. The way in which Gitea broke the trust of the community seems like it probably should be avoided nowadays.
reply