Inaki Fernandez 5397b7b6aa ci: add [skip ci] to 03.2/03.3 bot commits to stop the develop write-lock burst ...

The V2 pipeline is meant to advance only via its workflow_run chain
(03.1 -> 03.2 -> 03.3 -> 04.1), which [skip ci] does not affect. But 03.2 and
03.3 committed data/inventory.yaml WITHOUT [skip ci], so their bot pushes also
matched push: path triggers: 03.2 re-triggered itself (and 03.3 triggered it
backward) on data/inventory.yaml, and data/inventory.sql woke 05.1. That
redundant fan-out flooded the shared develop-git-write-lock group; with
cancel-in-progress: false GitHub keeps only one pending run per group, so
superseded runs were auto-cancelled (0 jobs, no logs) - e.g. run 29263339507.

Every other develop-pushing stage (03.1, 04.1, 05.1, 09) already carries
[skip ci]; this completes the pattern on the two stages that were missing it.
The workflow_run chain, schedule, and workflow_dispatch entry points are
unaffected.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-17 19:26:44 +02:00

..

workflows

ci: add [skip ci] to 03.2/03.3 bot commits to stop the develop write-lock burst

2026-07-17 19:26:44 +02:00

dependabot.yml

feat: implement Platinum Maintenance suite (Dependabot, Social Cards, Automated Triage) [skip ci]

2026-05-19 10:47:41 +02:00

PULL_REQUEST_TEMPLATE.md

chore: modernize CI/CD, UI aesthetics, and documentation

2026-05-20 10:03:32 +02:00