Task: Analyse all CI workflows and map each check to its local equivalent
Table of Contents
This page documents a task in the Absorb PR checks locally: targeted checks, local review, CDash submissions story. It captures the goal, current status, acceptance, and any notes or results.
Goal
Inventory every CI workflow and check that gates a PR today. For each check, decide its fate:
- Run locally before submit: which skill runs it, and when.
- Stay on GitHub: continuous builds and nightlies.
- Retire: checks that add little signal at PR time.
Define the change-classification rules the submit-PR skills will use: doc-only changes run the site build; C++ changes run the full build and ctest; anything else follows the rule table. The written analysis is the input for the implementation tasks that follow.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Absorb PR checks locally: targeted checks, local review, CDash submissions |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-08-11 |
Acceptance
- Every current CI check is listed with its fate: local, GitHub, or retired.
- The change-classification rule table is written down, with one rule per change type.
- The analysis is recorded in a doc that the follow-up implementation tasks reference.
Plan
The analysis is recorded in the
CI workflows and local checks
knowledge doc: the full inventory of PR-gating checks, the fate of each
(local / GitHub / retired), the change-classification rule table the
submit-PR skills use, and the open questions the implementation tasks
resolve. The story's * Decisions distills the durable choices at
close.
Notes
Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario, run
through the QA Validation Runner panel) that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
PRs
| PR | Title |
|---|---|
| #1960 | [agile] Analyse CI workflows and map each check to its local equivalent |
Review
| # | Comment summary | File | Decision | Notes |
|---|---|---|---|---|
| 1 | Story Status table stale: Now/Next still say "Not yet started" although the analysis is DONE and Decisions are recorded | story.org | accepted | Now/Next updated: analysis done, implementation tasks next |
Result
Analysis delivered (see the PRs table): every check that gates a PR today is inventoried with its fate — run locally, stay on GitHub, or retire. The change-classification rule table (docs / code / ci / python tooling, mixed = union) is written. The analysis lives in the CI workflows and local checks knowledge doc, which the follow-up implementation tasks reference. All acceptance bullets are met. The story stays STARTED: the implementation tasks that absorb the checks locally are added next.