|Hacker News, Reddit, Stack Overflow Stats|
No public GitHub repository stats available
No public GitHub repository stats available
|Description||Powerful collaboration, review, and code management for open source and private development projects.||Git and Mercurial code management for teams||Open source self-hosted Git management software|
|Why people like using this service||
|Companies using this service|
April 06, 2014 06:24
I love GitHub! They provide a completely free service for hosting, storing, and collaborating on code. Seriously, if you aren't using them, go sign up now.
Why GitHub is more friendlier than other services I've used.
March 23, 2014 23:10
For starters you can fork a repo, edit it online and send a pull request which is huge if its something very small that you want to commit. The whole pull request system, the UI and the UX are great. If I sent out a pull request that failed on travis CI then all I need to do is fix it in my fork and the original pull request will have these updates as well making it super easy for everyone involved. Overall a great service.
November 06, 2014 13:19
Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff, like Travis CI. But the command bar has disappeared...
July 07, 2015 23:15
It's the best tools I have ever used.
Best self hosted git repository manager
March 27, 2016 14:21
You cannot get easier setup and deployment with GitLab. The documentation is huge and many common use cases are covered. It has a Community Edition (CE, free, 100% open source) and an Enterprise Edittion (EE, see pricing). The CE is more than good enough. Although in the entreprise world, the EE is much better suited if, for instance, LDAP is needed. There is a Web UI that allows people to version their work without too much hassle. If you are a developer and have worked with git before this is really easy.
GitHub's git repositories, issues database (for tracking bugs & possible improvements) and pull requests (for peer reviews of code) are all used extensively.
The social aspect, issue tracking and PR's are a great way to code and have it visible, keep it alive. Plus the README's and Emoji's :-)
I used GitHub as a way of hosting and sharing the source code of the service and it enabled me to better control the source code.
Used Github for code study and quick-start for application development. Version Control and collaboration.
The project lives in its own repository. Nice workflow for developer and no need for client to get here. Every time the repository gets pushed a web hook triggers build system at Netlify.
Used for version tracking. Post-push hooks move statically uploaded pages into production space
GitHub is the place to share code with the community. We share tutorials developed from lessons we have learnt and for sample applications using our platform.
GitHub was where both technical and non-technical people collaborated on the source code, and was used with Buildkite and Heroku’s integrations for testing and deployment. Non-tecnical people on the project used GitHub’s web UI to update markdown files, replace images, and help edit typos and copy.
Used to host public code. We've don't put that much effort in open source for the moment. We're a startup :)
SCM. Utilize it for multiple sub projects of this project. Server. iOS client. NPM private module. ETL project. Analytics project. (They all deploy to different places so I keep them separate.)
We use github to host all our software, as well as customer-specific configuration and deployment.
As the public code repository to hold any forked libraries and/or frameworks that might have been integrated.
healthchecks.io is an open source project, and its source is available on GitHub. We use GitHub issues to track bugs and feature requests. We have received some substantial pull requests and are happy for that.
We make all of our changes through GitHub pull requests, which are each reviewed by at least one other developer.
One thing I really wish GitHub had: Trello-style kanban for Issues. There are a bunch of services and tools that add Kanban to GitHub Issues. But Trello just seems far better. If GitHub had it’s own kanban tool, I’d probably use it. Right now it’s pretty painful to try to tie cards to commits manually (when/if we remember to).
모든 소스코드는 github 에서 관리됩니다. github 는 단순히 git 저장소 뿐 아니라 소스코드와 관련된 다양한 통계와 이슈 트래킹을 지원합니다. github 하나면 프로젝트 관리가 거의 한 번에 해결됩니다.
for source control and issue management we use Github. We use git as well to push code out to Heroku
Yeah, so we use GitHub, and we basically use a variant of continuous deployment where when anyone merges in a feature that they’ve finished with, they ship it immediately, and we bundle it up as a build pack and send it to all of our EC2 servers... Any developer on the team can trigger a build and deploy at any time. So on a given day, we probably deploy 20 or 30 times to prod.
Best and simple source code management. In addition the backbone for the automatic deployment.
I use github for projects that I've open-sourced and are for public consumption. I also use this for other's projects I've forked.
Project management and version control. Great, fun tool that lets you easily integrate a distributed version control (with awesome tracking functionality) into your system.
All Pathwright repos are stored on Github. Some private, and a handful of open source projects.
Github Enterprise is our version-control overlay, managing code-reviews and facilitates code-merging, and has a great API.
"Having a CI server building all commits across all branches was a huge first step, but to make this useful we needed to surface the outcome of these builds. This is where GitHub’s commit status API comes in. Every time our CI server begins a build, it pings GitHub’s commit status endpoint, and every time it completes a build it hits the endpoint again with the outcome. Now every open PR includes a yellow/red/green indicator for the branch in question, with a direct link to the build status page on our CI server. In practice this means more transparency, faster feedback cycles, and a guarantee that every branch merged into master has a passing test suite. This integration has been a huge help in keeping our master branch green, and has thus greatly reduced our deploy times (since engineers aren’t waiting on build failures to be resolved in master)."
Used Bitbucket to manage small team's code in private repository.
I was looking for an alternative to GitHub, where I could store my own private repositories. BitBucket filled that need and has performed extremely well.
I use Bitbucket's git repositories as a low cost config sync between servers.
Using Git as the facto version control system, and free private repository to host the code.
The place for non-puiblic repositories. I appreciate their nice user interface and pricing model.
Bitbucket is used to host our git repositories in the cloud without the hassle of self-hosting.
GitLab is our main Git server, housed on a separate box inside our VPN, it's diverse features and sandbox-support allows it to be an extremely good way to secure your source code.
The version controlled repository to house all development and track any changes.