From 5deb5c18aa1e5d98b72fc35d65b66f9f6d45bd6a Mon Sep 17 00:00:00 2001 From: MSCodeBase Agent Date: Sat, 10 Oct 2026 21:28:45 +0300 Subject: [PATCH] ci: run CI for stacked PRs whose base is a feature branch The workflow listened only to pull_request -> main, so a stacked PR (base = feature branch) produced no CI run at all. That is exactly what happened to phases 2 and 3 of the migration: PR #74 and #75 were merged with a local clean-state run as the only evidence, and their status stayed unverifiable on GitHub. pull_request now also targets feat/**, exp/**, fix/**, chore/**. push stays main-only so one revision is never built twice. Job list unchanged (test, clean-state, manifest-parity, transport-equiv-e2e, docker-build); workflow yaml parses. --- .github/workflows/ci.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 4ee6f729..1bce281f 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -4,7 +4,11 @@ on: push: branches: [main] pull_request: - branches: [main] + # main — обычные PR. Ветки миграции — «stacked» PR (основа не main): + # без них CI не запускался, и фазы 2/3 уехали без единого зелёного прогона + # (2026-10-10, инцидент PR #74/#75). push по-прежнему только main, + # чтобы не задваивать прогоны для одной и той же ревизии. + branches: [main, 'feat/**', 'exp/**', 'fix/**', 'chore/**'] permissions: contents: read