From f9322348925e2999e64c17cd3d454d922572b9b2 Mon Sep 17 00:00:00 2001 From: npeter83 Date: Sun, 21 Jun 2026 05:53:06 +0200 Subject: [PATCH] ci: remove post-merge ci.yml workflow MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It duplicated the developer-machine quality gate (tsc + npm build + compileall), ran post-merge on main (not a pre-merge gate), and would put the heavy frontend build on the server on every push — the very load deploy.yml deliberately keeps on the dev box. The local pre-ship checks are the CI in this setup. --- .forgejo/workflows/ci.yml | 35 ----------------------------------- 1 file changed, 35 deletions(-) delete mode 100644 .forgejo/workflows/ci.yml diff --git a/.forgejo/workflows/ci.yml b/.forgejo/workflows/ci.yml deleted file mode 100644 index 680e9e8..0000000 --- a/.forgejo/workflows/ci.yml +++ /dev/null @@ -1,35 +0,0 @@ -name: CI -# Lightweight validation on every push to main: type-check + build the frontend and -# byte-compile the backend. The image build and rollout happen on the deploy host -# (see deploy/README.md); this just catches breakage early. -on: - push: - branches: [main] - workflow_dispatch: - -jobs: - frontend: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - - uses: actions/setup-node@v4 - with: - node-version: "20" - - run: npm ci - working-directory: frontend - - run: npx tsc --noEmit - working-directory: frontend - - run: npm run build - working-directory: frontend - - backend: - runs-on: ubuntu-latest - steps: - - uses: actions/checkout@v4 - - uses: actions/setup-python@v5 - with: - python-version: "3.12" - - run: pip install -r requirements.txt - working-directory: backend - - run: python -m compileall -q app - working-directory: backend