Git is a program your computer runs to have a single folder have source control. It does all the hashing and commit chaining that you’re used to, branches, that sort of thing.
But if you want it to be on more than one computer, you need to do this complicated “Bare” repository setup on a server computer to do the “git push” stuff you’re used to.
Most people, being too lazy to learn bare repositories and the general sysadmin necessary to host a git server themselves, instead just use Microsoft’s Github which is a web interface for the server use of git the program.
Microsoft then proceeded with their classic mantra of “Embrace, Extend, Extinguish” and started slapping on more and more features that are incompatible with any other git hosting service: actions, CI, their web VSCode instances, etc. That’s all in GitHub too. But it’s all just web interface for git the open source program, at the end of the day.
I like shitting on M$FT as much as the next bloke but if you believe Github started being evil when Microsoft entered the picture then your memory is pretty awful.
From it’s inception github pushed proprietary tagging and issue numbers that have no meaning outside their platform and a difficult export process to trap projects - especially commercial ones - on their platform.
I was being diplomatic because I was uncertain how people felt about the issue and PR tracking, considering how Bitbucket and GitLab replicate it. Felt simpler to focus on the since-M$ft egregious steps.
Just a few comments on this. Most people aren’t “lazy”, they just understand that the effort to run a bare repository is greater than basically any other solution. Also your incompatible features list implies that other git repo sites (gitlab, codecommit, bitbucket, etc) don’t have their own form of proprietary stuff that you have to learn. In fact the newest version of gitlab actually changes their web ide into vscode web, because of the obvious, it is much better than their old ide.
Git is a program your computer runs to have a single folder have source control. It does all the hashing and commit chaining that you’re used to, branches, that sort of thing.
But if you want it to be on more than one computer, you need to do this complicated “Bare” repository setup on a server computer to do the “git push” stuff you’re used to.
Most people, being too lazy to learn bare repositories and the general sysadmin necessary to host a git server themselves, instead just use Microsoft’s Github which is a web interface for the server use of git the program.
Microsoft then proceeded with their classic mantra of “Embrace, Extend, Extinguish” and started slapping on more and more features that are incompatible with any other git hosting service: actions, CI, their web VSCode instances, etc. That’s all in GitHub too. But it’s all just web interface for git the open source program, at the end of the day.
I like shitting on M$FT as much as the next bloke but if you believe Github started being evil when Microsoft entered the picture then your memory is pretty awful.
From it’s inception github pushed proprietary tagging and issue numbers that have no meaning outside their platform and a difficult export process to trap projects - especially commercial ones - on their platform.
I was being diplomatic because I was uncertain how people felt about the issue and PR tracking, considering how Bitbucket and GitLab replicate it. Felt simpler to focus on the since-M$ft egregious steps.
GitHub was independent from Microsoft for a long time, and was only acquired in 2018.
Just a few comments on this. Most people aren’t “lazy”, they just understand that the effort to run a bare repository is greater than basically any other solution. Also your incompatible features list implies that other git repo sites (gitlab, codecommit, bitbucket, etc) don’t have their own form of proprietary stuff that you have to learn. In fact the newest version of gitlab actually changes their web ide into vscode web, because of the obvious, it is much better than their old ide.