fix(advance-deploy-env): skip branch create/delete (prerequisite for #1274 staging)

[LukasWodka]

On a branch-creation push the before-hash is all-zeros → the range falls back to 'last 50 commits' → it advances ~50 recent PRs' kanban items. A branch creation merges nothing, so cutting a new staging branch (D8/#1274) would mass-move ~50 items per repo to FR on staging — the same corruption class as the default-branch incident.

Guards the advance job with github.event.created != true && github.event.deleted != true.

Must be on main before any staging branch is cut for #1274. Merge → promote to main → then create staging branches safely.

---

Note

Low Risk
Single conditional on a CI workflow; reduces incorrect kanban updates with no change to deploy or application runtime behavior.

Overview
Adds a job-level guard on the reusable advance-deploy-env workflow so the advance job does not run when the push event is a branch creation or branch deletion (github.event.created / github.event.deleted).

Without this, a new branch push still has before as the all-zero hash, which triggers the existing “last 50 commits” fallback in the PR-extraction step and can bulk-update many kanban items even though no new work was merged—e.g. when cutting a new staging branch for #1274.

^{Reviewed by Cursor Bugbot for commit 45941f3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

👋 Heads-up — Code review queue is at 40 / 30

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• .github#80 — feat(kanban): collapse FR on dev + Ready for staging → On dev (D6, code only) · author: @LukasWodka · no reviewer assigned
• averaging-service#207 — Promote develop → staging · author: @shujaatTracebloc · no reviewer assigned
• backend#1201 — docs(rfc): Data spaces & federated dataset composition (draft) · author: @LukasWodka · no reviewer assigned
• backend#1217 — docs(rfc): Dataset integrity & score reproducibility (draft) · author: @LukasWodka · no reviewer assigned
• backend#1228 — Promote develop → staging · author: @shujaatTracebloc · reviewer: @saadqbal
• backend#1244 — fix(experiments): surface save-time failures as 5xx + guard new NOT NULL columns · author: @LukasWodka · reviewer: @saqlainsyed007
• backend#1251 — docs(bugbot): add .cursor/BUGBOT.md project context (#930) · author: @LukasWodka · no reviewer assigned
• backend#1254 — docs(pr-template): owner-qualify cross-repo closing keywords · author: @LukasWodka · no reviewer assigned
• backend#1259 — docs(rfc): qualified RFC identifiers + org-wide index · author: @LukasWodka · no reviewer assigned
• backend#1261 — RFC-BACKEND-0008: board & process reset (decision RFC — for markup) · author: @LukasWodka · no reviewer assigned

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)

[LukasWodka]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 45941f3. Configure here.}