Skip to content

ci: run push workflows only on develop, cancel superseded runs - #294

Merged
extreme4all merged 1 commit into
developfrom
t3/ci-develop-only
Nov 14, 2026
Merged

extreme4all merged 1 commit into
developfrom
t3/ci-develop-only

Conversation

@extreme4all

Copy link
Copy Markdown
Contributor

Summary

  • Add branches: [develop] to the push trigger in all 17 project workflows; existing paths filters and every workflow_dispatch block are unchanged
  • Add a top-level concurrency block to the same files (group: ${{ github.workflow }}-${{ github.ref }}-${{ github.event_name }}, cancel-in-progress: true) so rapid re-pushes cancel superseded runs instead of stacking on the self-hosted runners
  • The github.event_name suffix keeps workflow_dispatch (deploy) runs in their own group, so a push to develop can never cancel an in-flight production deploy
  • Untouched: _common.yml, _build.yml, _deploy.yml, codeql.yml, sim.yml; gh workflow run <name> -f environment='deploy to prd' remains the production deploy entry point

Testing

  • All 17 modified YAML files parsed with yaml.safe_load; each verified to have push.branches == [develop], its original paths list, the exact concurrency group string, cancel-in-progress: true, and an intact workflow_dispatch
  • Diff review: 17 files, 119 insertions, 0 deletions; changes limited to on:/concurrency blocks in .github/workflows/*.yml project files
  • Dispatch smoke test: gh workflow run scraper_hiscore --ref t3/ci-develop-only -f environment=test was accepted by GitHub Actions (confirming the modified YAML is valid); run 43538923777 executed only the common / lock_file job — no build/deploy jobs, which gate on environment == 'deploy to prd'
  • Branch push spawned no new workflow runs, as expected: a commit touching only .github/workflows/** matches no project workflow's paths filter

@extreme4all
extreme4all merged commit 613cdaf into develop Nov 14, 2026
8 checks passed
@extreme4all
extreme4all deleted the t3/ci-develop-only branch November 14, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant