Branches
In Gitoqlok a branch is always backed by a Qlik app: the original app is on the main branch, each copy of it is on its own branch. This maps Git's isolation onto Qlik's "duplicate the app" habit.
Create a branch from a copy
Duplicate the app in Qlik
Use Qlik's own Duplicate on the hub (Qlik Cloud) or in the stream (Enterprise). If the app is published, make a copy to your personal space or Work area.
Open the copy and click the Gitoqlok icon
Gitoqlok reads the master ID stored in the app, finds the repository of the original and shows:
We found a repository for the master qlik application, from which current application was duplicated (repository link)
with a Create Branch button.
Name the branch
Click Create Branch, accept or edit the Branch Name (prefilled from the pattern in Repository Settings) and click Create. Gitoqlok creates the branch from the master app's branch and links the copy to it.
Tick Branch off from the branch that is used in the app you are duplicating from and pick a branch if the copy was made from another developer's copy rather than from the original — the new branch then starts from that branch instead of the main one.
From now on the copy commits to its own branch. The header shows the branch name next to the repository.
Duplicate App from the popup
The header menu next to Publish App offers Duplicate App. It duplicates the app in Qlik and connects the copy as a new branch in one step: enter the Branch name and an optional App name and click Duplicate. This is the quickest way to start a feature branch.
When the current app is a published copy whose master has a repository, the Create Branch button turns into Duplicate: Gitoqlok creates an editable duplicate and a branch for it, because published apps cannot be edited in place.
Connect an app to an existing branch
Use Connect to existing repository → To existing branch when the branch already exists (for example, another developer created it) and you want your copy of the app to follow it. Then click Update to load the branch's state into the app. See Create a Repository.
Switching branches
An app cannot switch branches; it is the branch. To see another branch's state, use the branch selectors in the Diff Viewer, Load Script Diff or Sheets Comparator, or import objects from that branch.
Merging
Merging happens on the Git provider: open a pull request from the feature branch into the main branch, review and merge. Then open the master app and click Update to apply the merged state. See Team Workflow and Update and Roll Back.
Keep branches
Do not delete branches after merging. Every branch is the history of a copy of the app and may be needed to roll back or to compare versions later.
