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

Investigate release mechanisms that do not require commit pushback #129

New issue
Open
opened 2026-05-26 05:07:07 +00:00 by coilysiren · 0 comments
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 added
P3
 and removed
P2
 labels 2026-05-31 07:00:39 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dispatch/issue-294
tangled-knot
dispatch/issue-216
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
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.