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
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.
Status: design decisions locked, implementation starts
Architecture decisions
.github/workflows/in each watched repo (Gitea Actions supports the GitHub Actions format).immediate. Prototypewindowvariant tracked in #32 for comparison.deploy/<stack>.registry.rudolf.keenetic.link). Deploy to swarm via docker stack deploy.brencher → brencher2
.github/actions/brencher/insideadmin/brencher(same repo, reuses existing code).Open questions (unblocked during implementation)