Great Source Code Control Tool for Distributed Teams
June 27, 2018
Great Source Code Control Tool for Distributed Teams
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with GitHub
GitHub is being used for the engineering group’s - primarily for software engineering and some DevOps scripts.
- GitHub is very strong on coding collaboration. Great tooling that enables distributed teams to work in an asynchronous manner.
- Excellent code repository & related tooling. Managing changes/pull requests from the UI is extremely simple.
- System uptime is incredible - you can rely on this for your company.
- Keeping issues with each project is extremely helpful.
- GitHub needs a higher level of project organization. Being able to group related projects and then handle project related issues vs specific module related issues would be incredibly useful.
- Native integration into CI/CD pipeline would be awesome
- User interface design could stand to be updated to feel fresh and improve UX a bit.
- Enable GitHub pages for private repos and keep them private
- Without GitHub, we wouldn’t have been able to easily setup distributed teams.
- GitHubs stability keeps developers productive.
- It enables asynchronous development so working across time zones is easy and cost-effective.
At the time to evaluation - Bitbucket was very tightly integrated into Atlassian’s suite of tools. For an organization that is starting out and looking to spend limited funds effectively - the cost/benefit of using that suite of tools usually doesn’t make sense. Granted things may have changed since then (its been over 5 years) - but at the time GitHub was effective - and all prospective engineers knew about it and already had accounts. This made it very easy to add to the organization and not lose time in training, etc. Developers seem to really love GitHub above most other tools out there - so that plays into the decision making as well.