Files

lucaronin 62c52c7266 ci: github pages with release history

Use peaceiris/actions-gh-pages@v4 to deploy a release history site.
The page fetches releases.json (also deployed) and renders each release
with date, notes, and download links for .dmg files.

This handles the gh-pages branch creation automatically on first run.
The page is available at https://refactoringhq.github.io/laputa-app/

Product decision: used fetch() to load releases.json at runtime instead
of inlining it, which is cleaner and avoids shell escaping issues with
release note content. The releases.json is deployed alongside index.html.

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

2026-02-23 10:42:15 +01:00

ci.yml

ci: add hotspot code health gate via CodeScene API (≥8.50 floor)

2026-02-22 15:01:47 +01:00

README.md

feat: add comprehensive documentation and CI/CD pipeline

2026-02-17 13:10:43 +01:00

release.yml

ci: github pages with release history

2026-02-23 10:42:15 +01:00

README.md

CI/CD Setup

GitHub Actions Workflow

Il workflow ci.yml esegue i seguenti check automatici:

1. Tests

Frontend: pnpm test
Rust backend: cargo test

2. Test Coverage

Frontend: vitest con coverage reporting
Threshold configurabile in vitest.config.ts

3. Code Health (CodeScene)

Delta analysis su ogni PR/push
Fail se il code health diminuisce
Richiede secrets configurati (vedi sotto)

4. Documentation Check

Verifica che se cambia codice in src/ o src-tauri/, anche docs/ viene aggiornato
Warning only — non blocca il merge, solo un reminder
Skip con [skip docs] nel commit message
Aggiorna docs solo se la modifica invalida architettura/astrazioni/design già documentati

5. Lint & Format

ESLint per frontend
Clippy + rustfmt per Rust

Setup Required

CodeScene Secrets

Aggiungi questi secrets nel repository GitHub (Settings → Secrets → Actions):

CODESCENE_TOKEN=<your-codescene-pat>
CODESCENE_PROJECT_ID=<your-project-id>

Il PAT di CodeScene è lo stesso che usi localmente (~/.codescene/token). Il project ID lo trovi nella dashboard CodeScene.

Coverage Thresholds

Configura in vitest.config.ts:

export default defineConfig({
  test: {
    coverage: {
      lines: 80,
      functions: 80,
      branches: 80,
      statements: 80,
      // Fail CI se sotto threshold
      thresholds: {
        lines: 80,
        functions: 80,
        branches: 80,
        statements: 80
      }
    }
  }
})

Local Testing

Prima di pushare, puoi testare localmente:

# Run all tests
pnpm test && cargo test

# Check coverage
pnpm test:coverage

# Lint
pnpm lint
cargo clippy
cargo fmt --check

# CodeScene (local)
codescene delta-analysis --base-revision origin/main

Workflow Triggers

Push: su main e branch experiment/*
Pull Request: verso main

Status Checks

Tutti i check devono passare prima di poter fare merge. Se un check fallisce, vedrai il dettaglio nei logs di GitHub Actions.