GitHub - the why and the why not
July 28, 2017

GitHub - the why and the why not

Rajesh P R Mangipudi | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with GitHub

Github is currently used by the applications and the data teams. The applications use it as a repo for their code. The data team uses it both for database deployments, for deploying across various environments and also as a .sql code change repo, using Redgate Source Control software.
  • Cloud based repo - don't have to worry about the storage
  • Many tools that work with Github so committing work is easier
  • Easy to setup the security for the repos
  • The merges are at the branch level, so every folder within the branch has to be merged. This means lot of colloboration or more branches.
  • Moving away from on premise VCS to Github meant that we need not be VPN'ed in. This was very helpful for remote developers
  • Github being on the cloud was helpful as we did not have to maintain the onpremise VCS server
  • Lot of publicly available code repos meant that we can clone other developers' works and look at their solutions
  • SVN and Tortoise
GitHub was cloud based - so we did not have to maintain the on premise VCS Server.
GitHub had public repos - so we could refer to other developers' code base.
GitHub is ideal for version control in cases where the project is worked upon by one team.
GitHub is not ideal for version control where there are sub projects worked by different disconnected teams - It can be done, either by lot of collaboration between teams/individuals or by creating lot of branches and merging them correctly.