Overall Satisfaction with GitHub
GitHub is primarily for managing software source control, issue tracking, developer collaboration, CI/CD. We use it for source control, peer review, and server-side merge, CI/CD capabilities like automated test suite running for PRs and merges. We use a separate issue tracking system, but for many projects GitHub's built-in issue system is adequate, it has advantages like automatic issue references and linking of issues to commits, PRs. GitHub also offers wiki pages per project, team organization, and one of my favorites is its free static website hosting service called (GH-pages). Their static hosting is capable of consuming Jekyll (Ruby on Rails) based projects on the server-side. Open-source repositories and organizations are free of charge with a 1GB limit per repo. A limited number of private repositories for individuals (not organizations) are also free. GitHub can perform security checks of the packages used by the project and even propose recommended fixes to those in the form of generated PRs. Speaking of automated PRs GitHub offers extremely easy few click solutions to contribute bugfix PRs to open source projects and other actions can be performed solely using the web front-end.
- Free hosting of open source projects and a limited number of private repositories as well for individuals.
- Free website hosting of statically generated websites or Jekyll Ruby on Rails-based projects.
- Issue tracking, pull request system.
- CI/CD capabilities.
- Enforcing rules like PR needs to be accepted for a merge and other team management and policy features.
- Widely adopted, large user base.
- Very friendly and easy to use UI, many tasks can be done through the web.
- Organizations without a paid plan cannot have private repositories.
- Free repositories have a size limit of 1GB.
- Support could be slow to respond.
- Migrating repositories to other services can be hard.
- Helped to enforce source control policies.
- Gave the opportunity towards CI /CD pipeline.
- Reliable.
Gitlab is the main competitor and they also have CI / CD capabilities, and also issue tracking, wiki. Gitlab supports static website hosting but does not offer dynamic Jekyll RoR server-side processing. The main advantage of Gitlab is that it offers private repositories for organizations as well and their space limit is 10GB (10x more than GitHub).
Another big competitor is Bitbucket which has also more generous private repository embracement policies. Bitbucket is under the umbrella of Atlassian, so if someone uses JIRA issue tracking, the integration would worth selecting Bitbucket vs Gitlab or GitHub.
If someone is focusing on dynamic server-side processing of freely hosted static websites, there are companies like Netlify, which allow other technology stacks besides Jekyll Ruby on Rails, like certain JavaScript-based static generators.
Do you think GitHub delivers good value for the price?
Yes
Are you happy with GitHub's feature set?
Yes
Did GitHub live up to sales and marketing promises?
Yes
Did implementation of GitHub go as expected?
Yes
Would you buy GitHub again?
Yes