Integrations branches_to_be_notified: protected behaviour with a protected default branch

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

I'm not sure if this falls under a bug or a feature request, i'm looking for some clarification.

We have several integrations set up for notifications, these are currently slack and pipelines-email. Our requirement is to receive notifications for protected branches/tags only, but not the default branch (which is also protected).

Example config:

 pipelines-email:
      recipients: "email_address@here.com"
      notify_only_broken_pipelines: false
      branches_to_be_notified: "protected"
      pipeline_events: true
 slack:
      webhook: "webhook_here"
      notify_only_broken_pipelines: false
      branches_to_be_notified: "protected"
      deployment_events: true
      pipeline_events: true
      tag_push_events: true

Note that branches_to_be_notified is set as: protected and not default_and_protected. However, because our default branch is also protected (like most I imagine), it's receiving notifications too. Is it possible to have notifications enabled for protected branches but excluding the protected default branch.

It seems there could be confusion around what protected and default_and_protected mean when the default branch is also protected.

https://docs.gitlab.com/ee/api/integrations.html#slack-notifications

Edited by 🤖 GitLab Bot 🤖