gitea.ref_name returns PR number for pull_request events, need to
use gitea.head_ref to get the actual branch name.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use git clone instead of actions/checkout (no Node.js in runner)
- Add Use Case 0 to P4: build custom runner image with Node.js
The stock forgejo/runner image lacks Node.js, so standard GitHub
Actions don't work in host mode. P4 now includes building a custom
runner image as the first step.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Create .forgejo/workflows/test.yaml with basic hello world workflow
- Update README.md with CI/CD section explaining Forgejo Actions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use host labels (ubuntu-latest:host) instead of docker://
- Remove RBAC (not needed for host mode)
- Simplify configmap (no container backend config needed)
Host mode runs jobs directly in the runner container, which is
acceptable since we control all workflows and the pod provides
isolation from indri.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Use k8s pods instead of Docker containers for job execution
- Add RBAC for runner to create/manage job pods
- Add ConfigMap with runner config for kubernetes backend
- Remove Docker socket mount (no longer needed)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- ArgoCD Application for forgejo-runner
- Deployment with Docker socket access for running workflow containers
- Secret template for runner registration token (via op inject)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Move app.ini to ansible template with secrets from 1Password
- Enable Forgejo Actions in config
- Add DEFAULT_REPO_UNITS with repo.actions
- Clean up unused MySQL database fields (using SQLite)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
