mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
20110debab
* fix(ci): fleet-branch push triggers close the absent-check gap; dispatcher claim prefilter PROVEN with API receipts: when the PM squash-merges a subtask PR into a branch that is itself another PR's head (GitService.merge_pull_request → GitHub's Merge API), the pull_request synchronize webhook fires unreliably (1 of 3 in the live sample) while plain push events fired 100% — so PR heads sat with ABSENT required checks that three review rounds mistook for green. CI, CodeQL, e2e-smoke, and panel-ci now also trigger on push to the fleet's branch types, deduped by a concurrency group keyed on head_ref||ref_name so a branch that is also a PR head never double-runs. Dispatcher churn: _route_unassigned_pm_task consults the claim guards' own predicate (TaskService.is_pending_claim_blocked, a public wrapper — no duplicated SQL) before routing, so dependency- or sequence-held tasks skip the tick with zero HTTP claim round-trips; fails open so a DB hiccup degrades to the old behavior. * chore(docs): reflow hard-wrapped prose inherited from the six-PR merge train * chore(foundation): regenerate lifecycle artifacts; reflow inherited prose --------- Co-authored-by: Renn F <rennf93@users.noreply.github.com>
81 lines
2.5 KiB
YAML
81 lines
2.5 KiB
YAML
name: Panel CI
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- master
|
|
# Fleet task branches: `pull_request`'s synchronize trigger doesn't
|
|
# reliably fire when a revision lands on a PR head via the merge API
|
|
# (see ci.yml for the live-proven receipts); `push` does.
|
|
- 'feature/**'
|
|
- 'bug/**'
|
|
- 'chore/**'
|
|
- 'docs/**'
|
|
- 'hotfix/**'
|
|
paths:
|
|
- 'panel/**'
|
|
- '.github/workflows/panel-ci.yml'
|
|
pull_request:
|
|
branches:
|
|
- master
|
|
paths:
|
|
- 'panel/**'
|
|
- '.github/workflows/panel-ci.yml'
|
|
workflow_dispatch:
|
|
|
|
# A fleet branch that's also an open PR head can get both a `push` and a
|
|
# `pull_request` run for the same commit; cancel the older one instead of
|
|
# burning two runners on identical work. `head_ref` (set only for
|
|
# pull_request) and `ref_name` (the short branch name, valid for push) both
|
|
# resolve to the SAME branch name, so the two event shapes share one group —
|
|
# plain `github.ref` would NOT (it's `refs/pull/<n>/merge` for pull_request
|
|
# vs `refs/heads/<branch>` for push, so it'd never collapse them).
|
|
concurrency:
|
|
group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
|
|
cancel-in-progress: true
|
|
|
|
jobs:
|
|
panel:
|
|
name: Panel (Next.js)
|
|
runs-on: ubuntu-latest
|
|
|
|
defaults:
|
|
run:
|
|
working-directory: panel
|
|
|
|
steps:
|
|
- name: Checkout code
|
|
uses: actions/checkout@v7
|
|
with:
|
|
# The release-readiness smoke test calls ``git describe --tags`` to
|
|
# find the most recent release tag. ``actions/checkout``'s default
|
|
# shallow + no-tags clone makes that return empty, which made
|
|
# ``test_gather_snapshot_reads_the_real_repo`` fail with
|
|
# ``last_tag is None`` even though master had a tagged v0.13.0.
|
|
# ``fetch-depth: 0`` clones full history; the default ``fetch-tags``
|
|
# would still skip tags on shallow clones, so we also pin it true.
|
|
fetch-depth: 0
|
|
fetch-tags: true
|
|
|
|
- name: Set up Node
|
|
uses: actions/setup-node@v6
|
|
with:
|
|
# pnpm 11 (pinned in panel/package.json via packageManager) requires
|
|
# Node >=22.13; Node 20 makes `pnpm install` fail the engines check.
|
|
node-version: '22'
|
|
|
|
- name: Enable corepack (pnpm)
|
|
run: corepack enable
|
|
|
|
- name: Install dependencies
|
|
run: pnpm install --frozen-lockfile
|
|
|
|
- name: Lint
|
|
run: pnpm lint
|
|
|
|
- name: Type-check
|
|
run: pnpm exec tsc --noEmit
|
|
|
|
- name: Test (vitest + coverage)
|
|
run: pnpm test
|