Skip to content

CI templates are not restricted to the default branch

One of the MRs launched on a tenant's tenant repo triggered a deployment of the tenant configuration, despite the . The deployment stage should only be ran when the CI is triggered on the default branch (e.g. main).

  • Restrict deploy stage of tenant CI to the default branch (which is the original problem encountered)
  • Restrict deploy stage of activity CI to the default branch (which I noticed is also an issue while investigating the root cause)
Edited by Matthieu Stombellini