Add Forgejo Actions workflows for CI/CD
Some checks failed
CI / test (push) Failing after 1s
CI / test (pull_request) Failing after 1s
Build Check / build-check (push) Failing after 3m28s
Build Check / build-check (pull_request) Successful in 4m44s

- Create CI workflow for automated testing on push/PR
- Create deployment workflow with secrets handling
- Use self-hosted runners with existing Node.js installation
- Support YouTube API key and AWS credentials from repository secrets

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Derek Slenk 2025-07-16 00:04:42 -04:00
parent 3461feb9a4
commit a0956c37cf
2 changed files with 86 additions and 0 deletions

37
.forgejo/workflows/ci.yml Normal file
View file

@ -0,0 +1,37 @@
name: CI
on:
push:
branches: [ main, master, feature/* ]
pull_request:
branches: [ main, master ]
jobs:
test:
runs-on: self-hosted
steps:
- name: Checkout code
uses: https://codeberg.org/actions/checkout@v4
- name: Cache node modules
uses: https://codeberg.org/actions/cache@v3
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
- name: Install dependencies
run: npm ci
- name: Run linting
run: npm run lint
- name: Run type checking
run: npm run typecheck
- name: Build application
run: npm run build
env:
# Use empty string for YOUTUBE_API_KEY during CI build
YOUTUBE_API_KEY: ""