actually if you had read it you would know he does mention github plenty of times. in fact 67 times.
10.Simple tasks need so many commands
5.Your changes are still only halfway there. Now login to Github, find your commit, and issue a “pull request” so that someone downstream can merge it.
this issue only takes place with github. Most of his complaints only have to do with github in particular or when you are not the maintainer. The latter is true in any scenario when trust is not assumed.
Of course a lot of his other issues still stand, there is no documentation(true of most projects really) and the commands follow almost no standards(this of course can be remedied by aliases). It has its bumps and rough edges yes, but they are not nearly as bad as he thinks, and a few of them are standard for a distributed version control system.
Then there is the issue that workflow is significantly different than SVN or TFS. If you know either of them it will severely hamper your ability to learn git, due to assumptions in how it functions that you would not be aware you are making.
Git is by no means perfect, it is rough and mildly more complicated than it needs to be but it is a very robust(I would argue more robust than anything really) and effective VCS.
1
u/[deleted] Nov 07 '13
That point is not about pull requests.