Automatic deploys on image build #1
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/lunch-money-k8s#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-22T11:08:26Z - https://github.com/coilysiren/lunch-money-k8s/issues/12
Today a deploy is manual:
coily exec lunch-moneyfrom the infrastructure repo after CI builds the image. Consider an automatic path - ashipjob indocker.ymlthat rolls the kai-server deployment after a successful image build, similar to coilysiren/repo-recall's docker workflow.Not urgent. Manual deploy is fine for a deployment of one, and arguably safer. File-and-defer until Kai decides she wants it.
Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag:
burndown-2026-06.