Basically Git is change control for your working directory. It is platform independent, you can install it on Windows, Linux, Mac whatever… and these people will all be able to work together using GIT. You can use GIT with a command line or with an application:

Why do I need this with Qlik Sense?

Essentially the answer is you don’t if your using Qlik out of the box…** BUT** if you want to try and build some extensions, mashups or have lots of different Qlik environments but only one responsible for extensions then understanding the fundamentals of GIT change control will be extremely valuable to you. It also gives you access to a wealth of open source projects that are available through Github.

In short, using GIT will give you an easy way to scale your team, change control your scripts, handle bugs and rollback when something goes wrong.

Why do I need this with Qlik?

Essentially the answer is you don’t if your using Qlik out of the box…** BUT** if you want to try and build some extensions, mashups or have lots of different Qlik environments but only one responsible for extensions then understanding the fundamentals of GIT change control before you shou toddle off and start building.

Here are some good reasons for using GIT change control for Qlik extensions:

  1. You can easilly rollback mistakes, unless you claim to be the perfect programmer, the likely hood is you will break many things as you journey towards the desired result.
  2. It is easier to work with others and share the workload of the app – something that presented a challenge in a traditional Qlikview implementation where we struggled to have multiple people working on an application at the same time.
  3. It is easier to deploy – you can quickly push to a production environment or to a source code repository and the auditors will be very happy.
  4. You can add comments for each change you make incase you get hit by a bus. Remember always look both ways.
  5. You can deploy different versions of the same extension to different environments easily.
  6. Easier to debug issues.
  7. Merging code becomes a dream.

For a deeper understanding check out this great post:

http://nvie.com/posts/a-successful-git-branching-model/

and do this great tutorial for beginners:

https://github.com/jlord/git-it