Glossary

Branches:

Separate lines of development within a repository, allowing developers to work on features or fixes for Qlik Sense applications without affecting the main codebase.

Clone:

The process of creating a local copy of a repository from a remote source using Code Management. It allows developers to work on Qlik Sense applications, including mashups, extensions, and Qlik scripts, independently.

Commit:

The act of saving changes to the local repository in Code Management for Qlik Sense applications, including modifications to mashups, extensions, and Qlik scripts. It is accompanied by a descriptive message summarizing the modifications made.

Job:

A predefined set of tasks or actions executed automatically within a CI/CD pipeline in Code Management for Qlik Sense applications, such as building, testing, or deploying code changes.

Master Branch:

The primary branch of a repository in Code Management for Qlik Sense applications, representing the stable version of the codebase. It is created by default and typically reflects the production-ready state of the Qlik Sense applications.

Merge:

The action of integrating changes from one branch into another within Code Management for Qlik Sense applications. It is typically used to combine feature branches with the master branch (the primary branch created by default).

Merge Request:

A formal request initiated by developers in Code Management for Qlik Sense applications to merge changes from one branch into another. It is often used to integrate feature branches with the master branch after development

Repository:

A storage location within Code Management where code and related resources for Qlik Sense applications, including mashups, extensions, and Qlik scripts, are stored, managed, and versioned.