Git enthusiast
December 14, 2017

Git enthusiast

Hugo Romani Cortes | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with GitHub

GitHub became 2 to 3 years ago the new standard developer repository. Like most companies, we came from CVS/SVN world which used to fit our needs but with some gaps. Thanks to the distributed architecture of Git, developers can now manage their own repositories and merge their modifications with master or dedicated branches. With modern tools and modern approach (CI/CD) GitHub is the perfect solution for multi developers teams. The process of pull request is now standard in our organization and enables better code quality with additional review step.
  • GitHub is capable of integrating with modern devops approach (ci/cd) and most of the tools in such flows (jenkins or Bamboo).
  • GitHUb is capable of generating notifications for specific cases (i.e. webhooks) that allow triggering builds or deployments.
  • GitHub is following the modern way of sharing content in public or private spaces. We can find the same ideas with dockerhub, vagrantcloud, etc...
  • Until now, we didn't face any limitations in our current job. The only evolution we foresee is an evolution of the command line cli which should be easier to use
  • An additional evolution would be around the documentation of repositories (i.e. README.md files) that should be more documented for nicer presentations.
  • The negative impact was at the beginning of the deployment of git into our organization. GitHub requested to developers to learn a new versioning approach with their constraints. From my point of view Git concepts are bit more complex than CVS or SVN.
  • The positive impact is an evolution of developer mindset. With modern tools and modern approach with are moving toward devops and can benefit from Git features.
Microsoft Team Foundation Server was too heavy and too complex for fast dvelopment. The integration with opensource build solutions (i.e jenkins) was not explored but the main feedback on this tool was its complexity.
CVS and SVN used to be standards in past years and fit perfectly our needs. The concept of tags and release was very appreciated and we expected the same possibilities from Git.
Git is now the combination of good features of these tools and is now the standard at Air France.
GitHub is becoming a standard for source control management. This job is well executed. A developer team can be small or large, each developer manages their own version of source code. The pull request allows to merge branches after manual code review.

GitHub is not appropriate for document versioning (i.e. Word, PDF, etc...) as we are not able to merge these kinds of documents. It's preferable to use alternative solutions (Alfresco, SharePoint, etc...)