Be able to set both tags triggers at the same time as branch filtering

[guplem]

Workflows Triggered Incorrectly on Tag Creation Across Multiple Branches

Description:
When creating tags in a repository with multiple workflows set up for different branches, both workflows are incorrectly triggered even if the tag is created in one specific branch.
The expected behavior is for only the workflow associated with the branch where the tag is created to be triggered.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

1. Create two workflows for an APP

2. Configure them with the same tag trigger but distinct branches ("dev" and "main"):

3. Push changes and create a new tag to one branch (for instance: "dev"):

4. See how both workflows get triggered:

Images of the triggers:
DEV

PRODUCTION

I expect the "trigger on tag creation" configuration to only be triggered if the "watched branch patterns" and the "watched tag patterns" are matched at the same time.

Expected results

Only the "Dev" workflow should be triggered.

Actual results

Both, the "Production" and "Dev" workflows are triggered:

Build id (optional)

6579cd5124d0a653beeb0d97

[dtrdic]

Hello @guplem, based on the Codemagic documentation that's expected behaviour. Check out this part

Note that the watched branch settings do not affect tag builds.

[dtrdic]

Unfortunately, there's no workaround for this. If both workflows are configured to trigger on tag creation, they will initiate regardless of the branch

[guplem]

Okay, I've created an issue to address this.

[guplem]

Since they have closed my issue, I am turning this discussion to an idea as disclosed in the issue's comment.

[dtrdic]

hey @guplem, yes for workfow editor is not possible to do it so this classifies as a feature request.
But actually, If you switch to codemagic.yaml this action is possible, so this could be your workaround. You will just have to define the triggering section like this for each workflow;

    triggering:
      events:
          - tag
      tag_patterns:
        - pattern: "*" 
          include: true
      branch_patterns:
      - pattern: main
        include: true

    triggering:
      events:
          - tag
      tag_patterns:
        - pattern: "*" 
          include: true
      branch_patterns:
      - pattern: dev
        include: true

just tried myself and it's working

[Ycoi]

Thanks for the idea @guplem! I’ll record this down and we’ll consider this when making other changes to the workflow editor.

As David said, if you are in a hurry, you can already do this if you switch to the yaml configuration which offers more flexibility also in other ways. In the long run we are looking into moving to the direction of improved onboarding and visual yaml editor instead of the current workflow editor. This to enable more of our users easy access to advanced options like this. So even though we will keep on maintaining and supporting the workflow editor, the yaml configuration is the more flexible and futureproof option.