3 ms·
It's true. Look at all the tooling and workflows that depend on GitHub. Issues, pull requests, code review, etc.. Combine it with integrated services that re
by donmcronald 6y ago
It's true. Look at all the tooling and workflows that depend on GitHub. Issues, pull requests, code review, etc.. Combine it with integrated services that require GitHub to run like Actions (CI) and Codespaces (dev env) and you start to see how it works.
In a few years it'll be normal for new developers to view a software project and a GitHub project as the same thing because the entire process from creating the project to publishing it (on Azure most likely) will happen via GitHub.
Saying that no one is dependent on GitHub is like saying a mechanic isn't dependent on their tools. Moving away from GitHub is like a mechanic walking out of the garage with a single crescent wrench (the git repo). Then you find out no one else sells any of the tools you know how to use and that the only option is to rent them from someone else (Atlassian or GitLab).
- kzrdude 6y agoThis is a good point; my projects don't depend on actions and codespaces (only PRs), so I haven't seen it. Random "good thing" addition: If CI and other features create more of a github lock-in, maybe they could implement cross-git features (like pull requests from gitlab) without that being a disruptive feature that reduces their monopoly situation.