Unexpected webhook behavior in monorepo with multiple Codemagic projects

[illidan-release]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

React Native

Steps to reproduce

1.	I have a monorepo with the following branches:
        •	release/prod/c1
        •	release/prod/c2
        •	release/prod/c3
2.	Each branch has its own codemagic.yaml with project-specific configuration.
3.	Each branch is mapped to a separate project in Codemagic: c1, c2, c3.
4.	I configured the webhook for project c1 in the repo.
5.	Pushing to release/prod/c1 triggers the build as expected.
6.	Pushing or merging to release/prod/c2 or release/prod/c3 also triggers the c1 webhook, which should not happen.

Expected results

Only commits or merges to release/prod/c1 should trigger the c1 webhook and build in Codemagic.
Each webhook should only react to its corresponding branch/project (1:1 mapping).

Actual results

The webhook configured for project c1 is also triggered by activity in unrelated branches: release/prod/c2 and release/prod/c3.

Build id (optional)

688d2911c13bc86f353aa5ce

[dam-ease]

Hello @illidan-release,
Could you share what your current codemagic.yaml configuration looks like in each of the branches? From your description, it sounds like the issue is related to how triggering is currently handled.
I tried reproducing your use case locally with three branches: main, target, and new_targ. Below is the triggering section I used in each of their YAML files to ensure that builds only run for push to the corresponding branch:

main branch

    triggering:
      events:
        - push
      branch_patterns:
        - pattern: main
          include: true
          source: true
        - pattern: target
          include: false
          source: false
        - pattern: new_targ
          include: false
          source: false

target branch

    triggering:
      events:
        - push
      branch_patterns:
        - pattern: main
          include: false
          source: false
        - pattern: target
          include: true
          source: true
        - pattern: new_targ
          include: false
          source: false

new_targ

    triggering:
      events:
        - push
      branch_patterns:
        - pattern: main
          include: false
          source: false
        - pattern: target
          include: false
          source: false
        - pattern: new_targ
          include: true
          source: true

Please let me know what your current config looks like and if my description here matches what you are trying to achieve.

[dam-ease]

Hello @illidan-release,
Sharing my reproduction case with you in case it helps in tracking down where the issue might be on your end or help me understand your use-case better. I have a monorepo configured with the folder structure as below:

apps/
   counter_app/
   test_apis/
   new_app/
codemagic.yaml

I have three separate branches as well counter_app, test_apis and new_app each with different codemagic.yaml file contents particularly pointing to each working_directory and triggering section, so for example a snippet of the codemagic.yaml file of the test_apis branch is as below:

workflows:
  ios-workflow:
    name: iOS Workflow 
    max_build_duration: 120
    working_directory: test_apis
    triggering:
      events:
        - push
      branch_patterns:
        - pattern: main
          include: false
          source: false
        - pattern: test_apis
          include: true
          source: true
        - pattern: counter_app
          include: false
          source: false

When I make changes to the code in my test_apis app and push to the test_apis branch, only the branch is triggered. This is the case for others as well.
Kindly help double-check with what you have, and don't hesitate to let me know how I can help further.

[illidan-release]

Hi @dam-ease — thanks for the follow‑up and the repro.

My scenario it’s a cross‑project (multiple Codemagic projects pointing to the same repo), not just multiple workflows inside a single project.

Context
• Projects:
• Client 1 (configured with 2 workflows)
• Client 3 (configured with 4 workflows)
• Branches: each client has its own branch (e.g., client1, client3).
• Config: both projects use codemagic.yaml from the repo (no custom path), with triggering.events: [push] and explicit branch_patterns to include only their own branch and exclude the others (include: false, source: false for non‑matching branches).

Problem

When I push to the Client 3 branch, all 4 workflows from the Client 3 YAML are triggered—but they run under the Client 1 project, which only defines 2 workflows locally. This looks like the scheduler is evaluating the pushed branch’s YAML across projects and attributing the resulting builds to the wrong project.

Evidence (failed build IDs in Client 1 project)
• 68966201c13bc86f356e2a5a
• 6896653ec13bc86f356e3747
• 6896653ec13bc86f356e3746
• 6896653ec13bc86f356e3745

What I already tried
• Ensured branch_patterns explicitly exclude unrelated branches (include: false, source: false).
• Confirmed there’s no wildcard catch‑all that includes everything.
• Verified only events: [push] are enabled (PR triggers disabled for this test).
• Re‑saved both projects, re‑created webhooks, and retried.
• Reproduced consistently today.

Hypothesis / Ask
• Hypothesis: For repos connected to multiple Codemagic projects, the scheduler may be reading the pushed branch’s codemagic.yaml and scheduling those workflows in every project attached to the repo, then attributing them to whichever project resolves first (in my case, Client 1). This would explain why 4 workflows (from Client 3 YAML) appear in Client 1.
• Questions:
1. Are triggers scoped at the project level, or does the repo webhook fan out to all projects and only later apply branch_patterns?
2. Is the YAML used for trigger evaluation taken from the pushed branch or from the project’s default branch?
3. Is there any known caching that could cause cross‑project YAML bleed?

I did try the in‑app chat but haven’t gotten actionable guidance yet. I can share sanitized YAMLs for both projects (Client 1 and Client 3) if that helps. If you can confirm expected scheduler scoping for multi‑project setups on a single repo, I can tailor a minimal public repro accordingly.

Thanks!

[dam-ease]

Thanks for sharing this.
I just responded to you via in-app chat. I'll drop a copy of the resolution here as well once it's resolved in case someone runs into similar issues.

[illidan-release]

Thanks for the update. I’ll follow up on the in-app chat and will keep an eye out for the resolution here so others can benefit from it as well.

[dam-ease]

Since this was the expected behaviour, I'll be closing this from here.