1. Home
  2. Version Control Software
  3. GitHub Reviews
  4. User Review of GitHub
GitHub - A ultimate tool for code version control and collaboration
October 09, 2019

GitHub - A ultimate tool for code version control and collaboration

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with GitHub

GitHub is the Version Control system used across the company by all the departments. It is hosted well within the company data center and every employee has a user created in the centralised GitHub. There are many organizations created for different projects/departments as per the need. Users can have both public and private repos in their own user profile. Though the user makes a public repo, it is still accessible only to people within the company as it is hosted inside datacenter and not accessible to open public. It is the recommended SCM across the whole company.
  • Branches are links and trees instead of a replica.
  • GitHub gists are very good and helpful for storing and referring commands and scripts.
  • Github pages lets user/organizations have static websites without a need for hosting services.
  • The transparency and fine grain access control for Pull Requests, including constraints on reviews and mergers are too very good.
  • The wide range of GitHub APIs help Automation engineers to automate lot of work flows, especially WebHooks.
  • Pricing. There are other tools like GitLab which have similar features and are free.
  • File size restrictions. File size cannot be greater than 100 MB.
  • The Project Management section of github is not very great.
  • One central tool for code management is absolutely a huge plus.
  • It is a good ROI as it has support for users, organizations and can have very good isolation between projects and teams.
  • Due to very good third party integrations, company can leverage them and focus on its actual objectives without worrying much about reinventing the supporting tools for automating the workflows. So it's a great win for the company.
The branches in Perforce and SVN are replicas instead of links/trees like in Github. Those two tools do not have rich APIs like that of GitHub. Subversion and Perforce do not support local repositories, which might hamper the development, if developer is coding and the tools are unreachable. GitHub solves this issue as it supports local and remote repositories, developer can code stuff and commit the changes in local repositories and can push to the remote server once it is reachable. There are very less third party integrations available for SVN or P4, whereas github has thousands of integrations readily available. GitHub is a clear winner.
They have a very active support team and are ready to help as and when required. The support is not that very costly and the Support Engineers are highly skilled in their domain. There were cases where we had to reach out to the support team for issues and always they were helpful in solving the issues asap.

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

From the developers view, it is a very good tool to track issues and write code accordingly. The lightweight branches help in the workflow a lot. Developers of a project can decide on one of the branching strategies and work well in collaborating without the worry of code and file integrity. Can have peer reviews with the fellow collaborators for better quality of code. It is well suited for projects with collaborators as less as 1 to quite big teams of 100s of collaborators.

From the Automation team perspective, Github has many APIs and third party integrations which help in automating the workflows like CICD. Teams can write apps on top of GitHub APIs to do more analytics on the developer productivity and much more.