Yes, that’s true for the git repo itself, but a git forge can provide a multitude of related services, including issues and pull request management, CI/CD pipelines, wikis, static content hosting, package registries, etc. which are not as easily migrated.
I honestly think wiki, static hosting, package registries etc. don’t belong on a git repo. Github has continuously extended their feature-set, but its caused vendor lock-in which I think is the point. How hard is it to spin up a web service to host static content? There are loads of good open source wiki projects, etc.
Depends on the point of the wiki I feel, if it’s project documentation it should be in git alongside the code, if it’s a generic “document store” then yeah there’s better storage backends than git.
Why do it yourself in a complicated way and poke holes in my firewall and security if I can use the existing infrastructure that is already a publiclly accessible web page to host just another one? ¯\_(ツ)_/¯
That’s the genius of git: it’s not tied to any website. Pull your repo from here and push it to there and you’re cooking.
Are you a git expert ?
The website around it is also just optional. You can dump git repos anywhere you want.
Of course the website is helpful and adds tooling, bit it’s an extra nonetheless
Yep, amazingly flexible. If Linus had only ever made git, he’d have gone down as one of the greats.
As opposed to also having made the most used kernel in the world?
They’re saying he was always famous and then did another thing that would make a person famous.
It is a weird phrasing then!
Yes, that’s true for the git repo itself, but a git forge can provide a multitude of related services, including issues and pull request management, CI/CD pipelines, wikis, static content hosting, package registries, etc. which are not as easily migrated.
I honestly think wiki, static hosting, package registries etc. don’t belong on a git repo. Github has continuously extended their feature-set, but its caused vendor lock-in which I think is the point. How hard is it to spin up a web service to host static content? There are loads of good open source wiki projects, etc.
Depends on the point of the wiki I feel, if it’s project documentation it should be in git alongside the code, if it’s a generic “document store” then yeah there’s better storage backends than git.
Why do it yourself in a complicated way and poke holes in my firewall and security if I can use the existing infrastructure that is already a publiclly accessible web page to host just another one? ¯\_(ツ)_/¯
Git forges provides a lot of features these days now. From Merge requests, forks, issues tracking, secret branches, to team management stuff.
A lot more stuff gets bolted onto but they are arguably more optional but for some are the point lol
Like ci/cd at the forge level is the best to me for dev centric flows