5 ms·
Github itself is a Github project, therefore using anything other than the API would be some code duplication. Merging, Pull-Requests, Branches, Issues: all thi
by badboy 14y ago
Github itself is a Github project, therefore using anything other than the API would be some code duplication. Merging, Pull-Requests, Branches, Issues: all this is already covered when using the normal API.
I'm sure it could be "more efficient" when having code explicitely for this purpose, but then again you have to maintain to different code bases which do the same.
- alexchamberlain 14y agoYou either maintain a codebase that calls out to the Github API or a codebase that calls out to Git? What's the difference?
- pbiggar 14y agoTheres a lot of things you can do in the API that you can't do in git. For example, pushes exist in the API, but don't really within git.
- andypants 14y ago> For example, pushes exist in the API, but don't really within git. `git push`?
- pbiggar 14y agoI was unclear, sorry. You can't tell what pushes have occurred in the past from a git repo, but you can with the GitHub API.
- alexchamberlain 14y agoI don't get it... The API is built on top of `git`!
- pbiggar 14y agoGitHub has lots of things that Git doesn't have. As well as recording pushes and making them available over the API, it records fork information, has concepts of users and organizations which dont exist in git, has pull requests, comments, and post-commit code review, an issue tracker, etc, etc, etc.