ci: trim ci.yaml to frontend quality gates
CI / test (push) Successful in 6s
Build (Dev) / build (push) Successful in 11s
CI / lint-and-typecheck (push) Successful in 7s
CI / build (push) Failing after 0s

lint/typecheck/test pass; the build job failed only on
actions/upload-artifact@v4, which Gitea Actions doesn't support. Drop the
artifact upload and the placeholder production deploy job (the real build +
deploy is build-dev.yaml's pull-based release). Keep lint, typecheck, test,
and a build compile-check.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Joshua King
2026-06-05 10:22:44 -04:00
parent 35136cb9ad
commit 53ed73ff6c
+8 -22
View File
@@ -1,4 +1,8 @@
name: CI/CD
name: CI
# Frontend quality gates (lint, typecheck, test, build-check).
# Actual build + deploy of the hub is handled by build-dev.yaml
# (pull-based release → Pi self-update).
on:
push:
@@ -23,6 +27,9 @@ jobs:
- run: npm ci
- run: npm test
# Verify the frontend compiles. No artifact upload — Gitea Actions
# doesn't support upload-artifact@v4, and build-dev.yaml produces the
# real, deployed artifact anyway.
build:
needs: test
runs-on: go-react
@@ -30,24 +37,3 @@ jobs:
- uses: actions/checkout@v4
- run: npm ci
- run: npm run build
- name: Upload build artifacts
uses: actions/upload-artifact@v4
with:
name: dist
path: cmd/server/src/dist/
deploy:
needs: build
runs-on: go-react
if: github.ref == 'refs/heads/main' && github.event_name == 'push'
environment: production
steps:
- uses: actions/download-artifact@v4
with:
name: dist
path: dist/
- name: Deploy static files
run: |
echo "Deploying to production..."
echo "Deploy target: /var/www/remote-rig/"
echo "Placeholder — configure deploy target before merging to main"