GitHub: a product so perfect it's become synonymous with Git
Overall Satisfaction with GitHub
GitHub is used by some development teams across our large organization, including our small web team. It's used as a central code repository for storing our website code and allows multiple developers to work on separate branches simultaneously, then merge those changes into the main branch once their work is finished. It also keeps a history of changes so we can tell who changed things and when they were changed.
Pros
- Seamless integration with Git. Although you can use Git without using GitHub, the two have become almost synonymous.
- It provides a nice web-based UI for interacting with your central Git repository.
- Facilitates working with multiple branches, forks, and pull requests—all different aspects of having multiple people working on the same code simultaneously.
Cons
- Honestly, I'm having a hard time coming up with any cons or things I would change.
- It has facilitated team collaboration and product development. We would have a very hard time working as a team on the same website without GitHub.
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
Comments
Please log in to join the conversation