In a continuous integration and deployment pipeline, when you use Pega as the repository in which to test and store rules, you can rebase your development application to obtain the most recently committed rulesets from the repository on the remote system of record (SOR).
For example, you publish a branch from your development application to a Pega repository on an SOR. This action starts a job on your continuous integration tool, such as Jenkins, which merges branches on the SOR. After the merge is completed, you can rebase the rulesets on your development application to obtain the merged rulesets from the SOR.
To rebase rules, you must merge branches to make changes to rules. Changes made to rules in an unlocked ruleset version will not be visible by the rebase functionality.
For more information about using branches and Pega repositories, see the PDN article Using branches with Pega repositories in a continuous integration and delivery pipeline or Pega Pipeline Manager.