GitHub Action: auto-deploy approved PRs #24

Open
opened 2026-08-30 21:29:54 +02:00 by hermes · 0 comments
Contributor

Status: design decisions locked, implementation starts

Architecture decisions

  • Q1 (where): per-repo action, located at .github/workflows/ in each watched repo (Gitea Actions supports the GitHub Actions format).
  • Q2 (batch window): start with immediate. Prototype window variant tracked in #32 for comparison.
  • Q3 (commit source): per-stack branch, e.g. deploy/<stack>.
  • Q4 (delivery): the action itself builds and deploys. Build target = Gitea Docker registry (registry.rudolf.keenetic.link). Deploy to swarm via docker stack deploy.
  • Q5 (deploy target): direct to prod.
  • Q6 (merge): manual merge after deploy succeeds.

brencher → brencher2

  • Q7: brencher2 lives as a reusable action at .github/actions/brencher/ inside admin/brencher (same repo, reuses existing code).
  • Implementation kicks off once the design is solid; unknowns will be resolved empirically.

Open questions (unblocked during implementation)

  • Q2 collision behavior (multiple approvals in same minute)
  • State location (PR label vs other)
  • Retry policy
  • Observability
  • Migration from brencher to brencher2
## Status: design decisions locked, implementation starts ## Architecture decisions - **Q1 (where):** per-repo action, located at `.github/workflows/` in each watched repo (Gitea Actions supports the GitHub Actions format). - **Q2 (batch window):** start with `immediate`. Prototype `window` variant tracked in #32 for comparison. - **Q3 (commit source):** per-stack branch, e.g. `deploy/<stack>`. - **Q4 (delivery):** the action itself builds and deploys. Build target = **Gitea Docker registry** (`registry.rudolf.keenetic.link`). Deploy to swarm via docker stack deploy. - **Q5 (deploy target):** direct to prod. - **Q6 (merge):** manual merge after deploy succeeds. ## brencher → brencher2 - **Q7:** brencher2 lives as a reusable action at `.github/actions/brencher/` **inside `admin/brencher`** (same repo, reuses existing code). - Implementation kicks off once the design is solid; unknowns will be resolved empirically. ## Open questions (unblocked during implementation) - Q2 collision behavior (multiple approvals in same minute) - State location (PR label vs other) - Retry policy - Observability - Migration from brencher to brencher2
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/brencher#24