codemagic-ci-cd / cli-tools

Various utilities to managing Android and iOS app builds, code signing, and deployment.
https://codemagic.io/start/
GNU General Public License v3.0
245 stars 42 forks source link

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

Closed guplem closed 9 months ago

guplem commented 9 months ago

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. This has been discussed in the Discussion 2264.

Steps to Reproduce:

  1. Create two workflows in a repository for an app. Each workflow should be configured for different branches (e.g., "dev" and "main").
  2. Configure both workflows to be triggered by the same tag creation event, but make sure each workflow is set for its specific branch.
  3. Push changes to one of the branches (e.g., "dev") and create a new tag on this branch.
  4. Observe that both workflows (for "dev" and "main" branches) get triggered, despite the tag being created only in the "dev" branch.

Expected Results: Only the workflow associated with the branch where the tag was created (e.g., "Dev" workflow) should be triggered.

Actual Results: Both the "Production" (main branch) and "Dev" (dev branch) workflows are triggered, despite the tag creation in the "dev" branch only.

helinanever commented 9 months ago

Hi @guplem . I'm going to close the issue as the problem you are describing is not related to the Codemagic CLI tools. Please follow up on the discussion you linked or consider posting a feature idea in Discussions.

guplem commented 9 months ago

Hi @guplem . I'm going to close the issue as the problem you are describing is not related to the Codemagic CLI tools. Please follow up on the discussion you linked or consider posting a feature idea in Discussions.

Sure, I will turn Discussion 2264 into an "idea".