Port website CI and secret scanning to Forgejo, leave GitHub-specific automation separate #68

New issue

Closed

opened 2026-07-08 16:41:37 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-08 16:41:37 +00:00

Collaborator

Why

website already has a mature GitHub Actions surface: tests, scheduled pulse refresh, automerge, and trufflehog. The missing part is Forgejo coverage on the canonical surface. The right first pass is selective porting, not a blind copy.

The repo needs Forgejo build and test coverage plus secret scanning. The GitHub-specific automation should be evaluated separately.

Requested workflow shape

Add Forgejo workflows for the repo's normal CI path and secret scanning.
Port the equivalent of the current config.yml build and test coverage.
Port trufflehog coverage.
Do not bundle GitHub-only automerge behavior into the Forgejo pass.
Treat the current pulse-refresh.yml as a separate design choice. If it is moved later, that should be an explicit follow-up with its own rationale around API commits, signing, and scheduler ownership.

Acceptance criteria

.forgejo/workflows/ exists with at least CI and trufflehog coverage.
Forgejo runs the site's normal build and test path on push and PR.
The initial Forgejo pass does not try to recreate GitHub-specific automerge behavior.
Any decision about pulse-refresh is documented rather than silently copied.

Dependency note

This should land last in the batch. It is not blocked by the other repos in code, but it is the easiest one to scope incorrectly because it already has an active GitHub automation story and only part of that story belongs on Forgejo.

Filed by ward agent advisor cross-repo fan-out from coilysiren/inbox#177 (part 7 of 7, ward#424). Upstream dependency: coilyco-gaming/eco-mods#4.

— Codex, via ward agent

## Why `website` already has a mature GitHub Actions surface: tests, scheduled pulse refresh, automerge, and trufflehog. The missing part is Forgejo coverage on the canonical surface. The right first pass is selective porting, not a blind copy. The repo needs Forgejo build and test coverage plus secret scanning. The GitHub-specific automation should be evaluated separately. ## Requested workflow shape - Add Forgejo workflows for the repo's normal CI path and secret scanning. - Port the equivalent of the current `config.yml` build and test coverage. - Port trufflehog coverage. - Do **not** bundle GitHub-only automerge behavior into the Forgejo pass. - Treat the current `pulse-refresh.yml` as a separate design choice. If it is moved later, that should be an explicit follow-up with its own rationale around API commits, signing, and scheduler ownership. ## Acceptance criteria - `.forgejo/workflows/` exists with at least CI and trufflehog coverage. - Forgejo runs the site's normal build and test path on push and PR. - The initial Forgejo pass does not try to recreate GitHub-specific automerge behavior. - Any decision about `pulse-refresh` is documented rather than silently copied. ## Dependency note This should land last in the batch. It is not blocked by the other repos in code, but it is the easiest one to scope incorrectly because it already has an active GitHub automation story and only part of that story belongs on Forgejo. --- Filed by `ward agent advisor` cross-repo fan-out from coilysiren/inbox#177 (part 7 of 7, ward#424). Upstream dependency: coilyco-gaming/eco-mods#4.  — Codex, via `ward agent`

coilyco-ops closed this issue

2026-07-09 16:39:31 +00:00

coilyco-ops referenced this issue

2026-07-09 16:50:08 +00:00

Bring website devtools and CI into the current ward/dev-base world #69