GitHub: Version Control for the Masses
Use Cases and Deployment Scope
We currently utilize GitHub as the default code repository host for clients who either don't have a current version control system or for internal projects that need hosting. It's primarily used across our whole delivery team, while projects from other departments may be hosted there as well.
Pros
- Github integrates really well with 3rd party systems, especially those used for continuous integration.
- Github provides a number of built-in tools to support the project management process.
- Github is ubiquitous in the sense that it's rare to find a platform or organization that hasn't used it, making it much easier for onboarding.
Cons
- Some of the extended features, like "Projects", can be a little too lightweight and users may spend too much time setting it up and not end up using it.
- The process for accepting invitations is kind of odd and doesn't always provide direct instructions to end-users.
Likelihood to Recommend
I believe because GitHub has become so ubiquitous, there aren't many technical or code-based projects it isn't suited for. Even for repositories that are strictly for documentation, it serves well as for revision controlled documents. There can be some limitations through the integration APIs that other platforms like GitLab may be able to fill better.
