test(deploy): validate Forgejo Actions end-to-end flow #189

Merged
lekss361 merged 2 commits from test/forgejo-deploy-flow into main 2026-05-15 21:55:05 +00:00
Owner

Trivial Caddyfile change to validate full deploy:

  1. Forgejo Actions runner подхватывает push
  2. Builds backend/worker/frontend images через docker buildx
  3. Push images to ghcr.io/lekss361/gendesign-*
  4. SSH deploy на Beget VPS
  5. Caddy reload + health check

После успешного prod deploy — revert.

Trivial Caddyfile change to validate full deploy: 1. Forgejo Actions runner подхватывает push 2. Builds backend/worker/frontend images через docker buildx 3. Push images to ghcr.io/lekss361/gendesign-* 4. SSH deploy на Beget VPS 5. Caddy reload + health check После успешного prod deploy — revert.
lekss361 added 1 commit 2026-05-15 21:44:14 +00:00
test(deploy): trigger Forgejo Actions deploy flow
Some checks failed
CI / backend (pull_request) Failing after 1m46s
CI / frontend (pull_request) Successful in 3m33s
6c008f8226
Trivial Caddyfile change to validate end-to-end deploy:
1. Forgejo Actions builds backend/worker/frontend images
2. Push to ghcr.io via GHCR_PAT
3. SSH deploy to Beget VPS (46.173.16.127:/opt/gendesign)
4. Caddy reload + health check

Revert this commit after successful deploy validation.
Author
Owner

Auto-review — verdict: approve (requires-human merge)

Scope: Caddyfile попадает в list requires-human per CLAUDE.md "Auto-merge scope" rules — даже trivial change нужен human approval.

Findings:

  • Caddyfile:64 — trailing comment, ноль функционального impact на reverse_proxy / TLS / routing
  • Никаких secrets / auth / structural modifications не тронуто
  • PR body явно описывает revert-after-deploy — приемлемый pattern для test scaffolding

Recommended action: human approval перед merge. После успешной валидации pipeline — открыть follow-up revert PR (не оставлять test comment в main permanently).


## Auto-review — verdict: approve (requires-human merge) **Scope:** Caddyfile попадает в list `requires-human` per CLAUDE.md "Auto-merge scope" rules — даже trivial change нужен human approval. **Findings:** - `Caddyfile:64` — trailing comment, ноль функционального impact на reverse_proxy / TLS / routing - Никаких secrets / auth / structural modifications не тронуто - PR body явно описывает revert-after-deploy — приемлемый pattern для test scaffolding **Recommended action:** human approval перед merge. После успешной валидации pipeline — открыть follow-up revert PR (не оставлять test comment в main permanently). --- <!-- gendesign-review-bot: sha=6c008f8 verdict=approve scope=requires-human -->
lekss361 added 1 commit 2026-05-15 21:50:43 +00:00
fix(tests): prefix unused _upserted vars per RUF059
All checks were successful
CI / backend (pull_request) Successful in 1m16s
CI / frontend (pull_request) Successful in 2m28s
5960368062
Two test functions in _grid_walk_category heartbeat tests unpack
(upserted, requests) tuple but only assert on requests count.
Ruff RUF059 flags unused upserted — prefix with underscore.
Author
Owner

Auto-review — verdict: approve

CI (backend 1m16s + frontend 2m28s).

Findings:

  • Caddyfile:64 — comment-only test trigger, planned revert per PR body
  • backend/tests/services/test_cadastre_bulk.py:1162,1197_upserted prefix корректно убирает ruff F841

Recommended: merge as-is. Не забыть открыть revert PR для Caddyfile после успешного prod deploy.


## Auto-review — verdict: approve CI ✅ (backend 1m16s + frontend 2m28s). **Findings:** - `Caddyfile:64` — comment-only test trigger, planned revert per PR body - `backend/tests/services/test_cadastre_bulk.py:1162,1197` — `_upserted` prefix корректно убирает ruff F841 **Recommended:** merge as-is. Не забыть открыть revert PR для Caddyfile после успешного prod deploy. --- <!-- gendesign-review-bot: sha=5960368 verdict=approve ci=success -->
lekss361 merged commit 50547dcbb3 into main 2026-05-15 21:55:05 +00:00
lekss361 deleted branch test/forgejo-deploy-flow 2026-05-15 21:55:05 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lekss361/gendesign#189
No description provided.