From 67b204c0c9f4b6e7dcfcbd1652673e39178136a6 Mon Sep 17 00:00:00 2001
From: lukasWuttke <54042461+LukasWodka@users.noreply.github.com>
Date: Sun, 26 Jul 2026 19:03:02 +0200
Subject: [PATCH] fix(advance-deploy-env): skip branch create/delete pushes
 (#81)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On a branch-CREATION push the before-hash is all-zeros, and the range logic
falls back to 'the last 50 commits', extracting and advancing every PR ref in
them. A branch creation merges nothing — the commits are inherited from the
source branch — so this mass-advances ~50 recent PRs' kanban items on every new
branch. That makes cutting a new 'staging' branch (D8/#1274) corrupt the board,
the same class as the default-branch-change incident.

Guard the advance job with 'github.event.created != true && github.event.deleted
!= true'. A create/delete is not a deploy event.

Prerequisite for #1274 (create staging in every repo) — must be on main before
any staging branch is cut.
---
 .github/workflows/advance-deploy-env.yml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/.github/workflows/advance-deploy-env.yml b/.github/workflows/advance-deploy-env.yml
index a67fd9b..8fa6038 100644
--- a/.github/workflows/advance-deploy-env.yml
+++ b/.github/workflows/advance-deploy-env.yml
@@ -38,6 +38,12 @@ on:
 
 jobs:
   advance:
+    # A branch CREATION or deletion is not a merge — its commits are inherited,
+    # not newly shipped. Without this guard, creating a branch (BEFORE = zero
+    # hash) falls through to the "last 50 commits" range below and mass-advances
+    # ~50 recent PRs' kanban items — e.g. every time a new `staging` branch is
+    # cut for a repo (RFC-BACKEND-0008 D8/#1274). Skip create/delete pushes.
+    if: github.event.created != true && github.event.deleted != true
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4