coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Investigate release mechanisms that do not require commit pushback #129

New issue
Closed
opened 2026-05-26 05:07:07 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-26 05:07:07 +00:00
Owner
Copy link

The current Caddy / Forgejo Actions pipelines regenerate config snippets and commit them back to main. This recurring pushback breaks main-line sync between Forgejo and GitHub (Forgejo-Actions commits are unsigned, GitHub ruleset rejects them) and creates noise in the commit log.

Investigate alternatives that produce release artifacts without writing to the repo:

  • Generate artifacts into a release / object store (S3, Forgejo releases, GitHub releases) and pull at deploy time.
  • Render snippets at runtime instead of committing them.
  • If pushback is unavoidable, configure Forgejo Actions to sign commits using a GPG key registered to the bot identity, so signature-required rulesets accept them.

Motivated by todays Docker Hub move running into the GitHub-side push reject.

The current Caddy / Forgejo Actions pipelines regenerate config snippets and commit them back to main. This recurring pushback breaks main-line sync between Forgejo and GitHub (Forgejo-Actions commits are unsigned, GitHub ruleset rejects them) and creates noise in the commit log. Investigate alternatives that produce release artifacts without writing to the repo: - Generate artifacts into a release / object store (S3, Forgejo releases, GitHub releases) and pull at deploy time. - Render snippets at runtime instead of committing them. - If pushback is unavoidable, configure Forgejo Actions to sign commits using a GPG key registered to the bot identity, so signature-required rulesets accept them. Motivated by todays Docker Hub move running into the GitHub-side push reject.
coilysiren commented 2026-06-17 08:22:41 +00:00
Author
Owner
Copy link

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.

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`.
coilysiren 2026-06-17 08:22:42 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
coilyco-flight-deck/infrastructure#129
No description provided.