Problem: Registry login fails silently if secrets aren't configured
- Empty FORGEJO_REGISTRY_USER/TOKEN → docker login hangs/fails
- No clear error message about missing credentials
Solution: Add validation step that checks credentials exist
- Fails early with clear error if secrets missing
- Shows how to configure in repo settings
- Uses direct secret injection (not via env vars)
- Isolates docker config to /tmp/docker-config
Result: CI will fail fast with actionable error if credentials missing
Merge fix/memory-ci-nodejs-docker into main to enable CI triggers.
## Changes
- Add Node.js install before actions/checkout@v4
- Add docker.io install before docker login
- Add env vars (REGISTRY, REGISTRY_USER)
- Test job runs on all branches + PRs ✅
- Build-push job only runs on main push ✅
## Result
- PRs: CI runs tests (no registry push) ✅
- Main push: CI runs tests + builds + pushes to registry ✅Reviewed-on: rock/poimen-memory#17
Co-authored-by: rock <[email protected]>
Unified pattern enforced:
- test job: runs on all branches + PRs
- build-push job: only on main push, depends on test
- Proper env vars (REGISTRY, IMAGE)
- Install Node.js before checkout
- Install docker only in build-push (conditional)
- Docker login + build + push + prune
See `CLAUDE.md` for project context and constraints.
See `CLAUDE.md` for project context and constraints.
# CI test 1788759975
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.