Along the same line of thought: there's a lot of momentum regarding tooling surrounding GitHub. Continuous integration works smoothly. Slack works smoothly. github/hub and ghi let you interact with the issues and repos from the command line. Vim, Emacs, Atom, and Sublime plugins exist to integrate with GitHub. While moving to another hosting platform might fix some things, there is a lot of solid tooling built around GitHub.
Github is more than a Git repository host. It provides other services for coordinating software development as well as a continuous integration service.
Yes, but Github is not just about Git hosting, it's about all those awesome social tools. If you use Issues as the main bug tracker, for example, you've got a problem.
Once you know how git/hub works, it seems much easier to me to use github, but I understand that not all people do; while all the other sites (squarespace, wix etc) are too much of "website builders". Fine thanks
Everyone is saying: just work on your local repo. But GitHub is way more than just git. There's bug tracking, code review, continuous integration, etc etc.
Making your organisation too dependent on a remote service can indeed be a scary prospect and I'm not sure what GitHub offers to mitigate this.
If you host your own Git repo(s), make sure you have someone on your team that can stop what they're doing at the drop of a dime and fix/tweak the server hosting the repo(s). Hosting it yourself, it will be 100% someone on your teams responsibility.
With Github (which is what we use). It's just there. It works perfectly. We get all the tools that come along with working on GH. We haven't seen one uptime issue since we started with them. They have an entire team to make sure everything is working properly, you do not.
No disagreement from me, so I don’t know what that snippet is telling you. I wasn’t saying GitHub or any other service is the greatest, I was only saying that using the GitHub site mixes GUI and CLI workflows, since using GitHub is so common.
In some sense that goes to the point that CLI can be better than some GUI tools. The ascii railroad diagram you get with git log might be preferable to what GitHub can do.
I've been using Hub[1] (though not aliased to `git`) for years now, and it's PR management capabilities have been invaluable working on larger projects. Hopefully GitHub CLI is as stable and reliable!
It looks like the main features I use from Hub are already well-supported in the GitHub CLI, and it looks like whether or not Hub will still be maintained is an open question[2].
Edit: Just noting that `brew install github` doesn't work, it's actually `brew install github/gh/gh` — that's a new format for brew packages I haven't seen before.
They don’t seem to plan to use any of the GitHub features. They only use it as a “cloud git hosting”. My guess is if there was as reliable git-web hosting they might as well go with it. By only using GH for repo hosting they’re not locking in themselves and also outsource the tedious parts (infra, backups, etc.).
I work on OpenJDK. Here are some steps we've taken to not overly depend on GitHub:
1. Issues stay on a self-hosted JIRA.
2. All PRs get an automatically generated patch that's posted to the mailing list, and all comments are two-way mirrored between GH and the mailing list.
3. All links to commits in issues don't point directly at GH but at an indirection through our domain.
4. All bots work on both GH and GitLab
This means that we can move off of GH pretty much instantly if the need arises. But self hosting with GitLab just wouldn't serve our goals. We want speed all around the world, and we don't want to spend resources on administration.
So on a team I manage, we've used github::fi (github enterprise looks to be the next evolution) for the past year. If you don't have an option to put code out onto github.com, then it's great to essentially have github.com inhouse - minus of course all the public repos.
We find it's the developers go-to place, so using the wiki along with where the source is hosted, is fantastic. As a dev team manager, I love the browsing the codebase via the web browser, reviewing what's going on in the code base instead of pulling down code locally.
From a customer, if you've got the funds, and can't go with github.com hosted, then it's the next best thing. It's been rock solid.
Why do you need a centralized hub? Most repos on github are entirely unrelated to eachother. Repos can be self hosted. Issues can be tracked on your own website. You don't need a megacorp to run a website. If you are writing open source tooling you are more than qualified to roll your own here.
reply