"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)."

GitHub is a Web-based Git version control repository hosting service. It is mostly used for computer code. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project

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.

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 is a web-based hosting service for version control using Git. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.

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.

We use Bitbucket and Bitbucket Pipelines because of its tight integration with JIRA and code authorization features.

The primary drawback is that its extension ecosystem (e.g., PR review tools) is miles behind Github

I use CodeCommit for projects that require a tighter integration with the AWS ecosystem.

Otherwise, my default source control system as a service of choice is: GitHub.

Best GIT repository management software that allows free closed-source projects. Also works seamlessly with other Atlassian products.

Great private repository capabilities that can be used for continuous integration in conjunction with Jira and Bamboo.

had to use it as a couple of clients had repos on it. worst of the git services. i try to stay far far away.