From b94bd1ffefd2257e4986f590add940bfc42f1114 Mon Sep 17 00:00:00 2001
From: berfinyuksel <99557970+berfinyuksel@users.noreply.github.com>
Date: Thu, 23 Jul 2026 11:06:50 +0200
Subject: [PATCH] Studio Frontend Build: scope push trigger to version branches
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The build workflow triggered on both push and pull_request. On a PR branch both
events fire and resolve to the same concurrency group, so cancel-in-progress
cancels one of them — surfacing as confusing cancelled "(push)" checks and a red
"some checks were not successful" on PRs even though the pull_request run passed.

Scope the push trigger to version branches (which have no PR); PR/feature branches
are covered by pull_request. Each branch now triggers exactly one run: visible,
green, no self-cancellation, and no non-fast-forward race.
---
 .github/workflows/studio-frontend-build.yaml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/.github/workflows/studio-frontend-build.yaml b/.github/workflows/studio-frontend-build.yaml
index b526e878fd..d7cd7e7d2c 100644
--- a/.github/workflows/studio-frontend-build.yaml
+++ b/.github/workflows/studio-frontend-build.yaml
@@ -1,7 +1,14 @@
 name: "Studio Frontend Build"
 
 on:
+  # Push builds run only on version branches (which have no PR). Feature/PR
+  # branches are covered by the pull_request trigger below — this avoids a
+  # push run and a pull_request run landing in the same concurrency group and
+  # cancelling each other (which surfaced as confusing cancelled "(push)" checks).
   push:
+    branches:
+      - "[0-9]+.x"
+      - "[0-9]+.[0-9]+"
     paths:
       - "assets/**"
   pull_request: