Maity: Board

ci: one ci run on main at a time, only the newest waits (concurrency group)

tsk-60fdjjq2w1hj done Maity OPS Team (maity-ops-team)

Oliver approved (req-8zh1rkez993w, 2026-10-31): the main ci runs piled up (12 queued, one per merge), each checking an outdated commit and holding runners the PRs waited on; A cancelled them by hand.

.github/workflows/ci.yml:18-20 today: group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.sha }}, cancel-in-progress only for pull requests. On main every sha is its own group, so nothing is ever replaced.

Proposal: on push to main use one group (e.g. ${{ github.workflow }}-main) with cancel-in-progress: false: GitHub then keeps the running main run and replaces any pending one by the newest, so at most one runs and one waits. Pull requests unchanged. Note in the KTW why not cancel-in-progress: true on main (a busy merge streak would never finish a main run, and a deploy needs a green one).