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

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 the

priority

label

2026-06-04 08:16:54 +00:00

coilysiren commented

2026-06-17 08:22:41 +00:00

Author

Owner

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