coilyco-gaming/eco-mods
2
0
Fork 0
Code Issues 2 Pull requests Projects Releases Packages Wiki Activity Actions

Add Forgejo CI for eco-mods without a Unity build pipeline #4

New issue
Closed
opened 2026-07-08 16:41:36 +00:00 by coilyco-ops · 2 comments
coilyco-ops commented 2026-07-08 16:41:36 +00:00
Member
Copy link

Why

eco-mods is an active mixed-tree repo. The public mods/ subtree is a real C# and Python codebase with a legacy GitHub trufflehog workflow, while the repo also carries large Unity asset trees that are not a good fit for headless Forgejo builds.

The missing coverage is not "full build everything". It is "validate the code-bearing parts and keep Unity out of the first pass".

Requested workflow shape

  • Add a Forgejo workflow that runs on push to main and on pull requests.
  • Validate the root hygiene baseline.
  • Validate the mods/ subtree's deterministic code path, including its dotnet build surface and any stable Python checks already used there.
  • Port or replace the existing GitHub-only trufflehog coverage with Forgejo-native coverage at the repo level.
  • Do not add a Unity build job.
  • Do not make CI depend on external game-server state.

Acceptance criteria

  • .forgejo/workflows/ exists with CI coverage for the code-bearing parts of the repo.
  • The workflow validates mods/ and root hygiene successfully in Forgejo.
  • Unity asset trees are explicitly out of scope for the first CI pass.
  • Secret-scan coverage exists in Forgejo rather than only under the legacy GitHub workflow.

Dependency note

This should land after the simpler repo patterns in factorio-mods, agentic-os-hardware, eco-ops, and sirens-discord-ops. It is the most nuanced repo in the batch because it mixes C#, Python, generated assets, and Unity content.

Filed by ward agent advisor cross-repo fan-out from coilysiren/inbox#177 (part 6 of 7, ward#424). Upstream dependency: coilyco-gaming/sirens-discord-ops#25.

— Codex, via ward agent

## Why `eco-mods` is an active mixed-tree repo. The public `mods/` subtree is a real C# and Python codebase with a legacy GitHub trufflehog workflow, while the repo also carries large Unity asset trees that are not a good fit for headless Forgejo builds. The missing coverage is not "full build everything". It is "validate the code-bearing parts and keep Unity out of the first pass". ## Requested workflow shape - Add a Forgejo workflow that runs on push to `main` and on pull requests. - Validate the root hygiene baseline. - Validate the `mods/` subtree's deterministic code path, including its `dotnet build` surface and any stable Python checks already used there. - Port or replace the existing GitHub-only trufflehog coverage with Forgejo-native coverage at the repo level. - Do **not** add a Unity build job. - Do not make CI depend on external game-server state. ## Acceptance criteria - `.forgejo/workflows/` exists with CI coverage for the code-bearing parts of the repo. - The workflow validates `mods/` and root hygiene successfully in Forgejo. - Unity asset trees are explicitly out of scope for the first CI pass. - Secret-scan coverage exists in Forgejo rather than only under the legacy GitHub workflow. ## Dependency note This should land after the simpler repo patterns in `factorio-mods`, `agentic-os-hardware`, `eco-ops`, and `sirens-discord-ops`. It is the most nuanced repo in the batch because it mixes C#, Python, generated assets, and Unity content. --- Filed by `ward agent advisor` cross-repo fan-out from coilysiren/inbox#177 (part 6 of 7, ward#424). Upstream dependency: coilyco-gaming/sirens-discord-ops#25. <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 16:34:10 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-eco-mods-4 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T16:34:08Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)
  • Resolved: coilyco-gaming/eco-mods#4 · branch issue-4 · harness codex · workflow direct-to-main
  • Run: engineer-codex-eco-mods-4 · ward v0.493.0 · dispatched 2026-07-09T16:34:08Z
  • Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-eco-mods-4` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T16:34:08Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-gaming/eco-mods#4` · branch `issue-4` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-eco-mods-4` · ward `v0.493.0` · dispatched `2026-07-09T16:34:08Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 16:41:22 +00:00
Author
Member
Copy link

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped by --skip-review / --no-review-gate

Implemented a Forgejo-native CI gate in .forgejo/workflows/ci.yml that keeps Unity build work out of the first pass and covers root hygiene, mods/ Python syntax, mods/ dotnet build, and repo-level TruffleHog. Replaced the legacy GitHub-only TruffleHog workflow and added a repo-level features note in docs/FEATURES.md.

Felt straightforward. The only local gap was that this container does not have dotnet, so CI validation is pinned to the workflow design rather than an in-container build run. Confidence is high. No surprises beyond that environment gap.

Follow-up: none.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: skipped by --skip-review / --no-review-gate Implemented a Forgejo-native CI gate in `.forgejo/workflows/ci.yml` that keeps Unity build work out of the first pass and covers root hygiene, `mods/` Python syntax, `mods/` `dotnet build`, and repo-level TruffleHog. Replaced the legacy GitHub-only TruffleHog workflow and added a repo-level features note in `docs/FEATURES.md`. Felt straightforward. The only local gap was that this container does not have `dotnet`, so CI validation is pinned to the workflow design rather than an in-container build run. Confidence is high. No surprises beyond that environment gap. Follow-up: none. </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
  
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
priority tier

  
P1
priority tier

  
P2
priority tier

  
P3
priority tier

  
P4
priority tier

No labels
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-gaming/eco-mods#4
No description provided.