Skip to content

How Version Control Works ​

Qlik Cloudsupported Qlik Sense Enterprisesupported Git serverrequired

Comparing approaches first? Version Control for Qlik Sense and Qlik Cloud explains what Qlik provides out of the box and how Gitoqlok differs from QVF exports, automations and DevOps platforms.

The model in one picture ​

Qlik app "Sales"  ───────────────────  repository gitoqlok-Sales, branch main
   │ duplicate in Qlik
   └─ copy "Sales(1)" (Anna) ────────  branch anna
   └─ copy "Sales(2)" (Bob)  ────────  branch bob
  • One app = one branch. A Qlik app is linked to exactly one repository and one branch. The first app you connect gets the default branch (main or master, as the provider creates it).
  • A copy of the app = a new branch. When you duplicate the app in Qlik and open the copy, Gitoqlok recognises the original (the master app) and offers to connect the copy as a branch of the same repository. Developers work on their copies and branches, then merge with a pull request on the Git provider.
  • A commit = a restore point. Every commit stores the complete serialized state of what you selected (script, objects, bookmarks, attached files). Any commit can be applied back to the app with Update.
  • Local changes = the app compared to the last commit. The Local Changes tab shows what was added, deleted or changed in the app since the selected commit.

The link between an app and its repository and branch is stored inside the app, so it survives exporting, publishing and duplicating the app — this is how a copy knows which app it was duplicated from. Gitoqlok also writes the app ID into the repository description on the Git provider; do not edit that description by hand.

If the link is lost (for example, the app was rebuilt from scratch), use Connect to existing repository to relink.

What happens on commit and update ​

  • Commit reads the app through the Qlik Engine API, serializes it to JSON and pushes the files that changed to the branch. Depending on the provider this is one commit or, for very large apps, several parts.
  • Update downloads the selected commit (as a repository archive to save API calls), compares it with the app and applies the differences: creates missing objects, updates changed ones and removes objects that are absent in the commit. The app is saved afterwards.

Both operations work on the design of the app. Data is never committed unless you explicitly export a QVF; a reload after an update is optional (Deploy from Git can run one for you).

Where each operation lives ​

OperationWhere
Create or connect a repository, create a branchPopup / side panel header and Local Changes tab
CommitLocal Changes → Save changes
Update, roll backCommit selector + Update
Import objects from other repositoriesImport tab
Create an app from a repositoryHub popup → Deploy from Git
Bulk create repositories for many appsOptions → Git Servers → Apps Manager or hub popup
Visual comparison of versionsQlik Helper: Time Machine, Diff Viewer, Sheets Comparator, Load Script Diff

Continue with Create a Repository.

Gitoqlok by Motio