Explicitly set the stable branches when pulling updates (!165) · Merge requests · infrastructure / ci-package-builder

Emanuele Aina requested to merge wip/em/merge-updates-explicitly-set-stable-branches into master Apr 13, 2021

Rather than relying on the format of the branch name, explicitly configure which branches should be considered stable. This allows us to land updates to apertis/v2022 directly before v2022.0 is released, rather than having all of them go to apertis/v2022-updates.

This is currently useful for downstream pulling updates from apertis/v2021 before their v2021.0 is released.

Task: T6873

Explicitly set the stable branches when pulling updates

Merge request reports