Document CI gotchas and standardize FORGEJO_TOKEN across skills #16

Open
opened 2026-02-17 18:49:35 +00:00 by mik-tf · 0 comments
Member

Context

During CI setup for freezone backend and frontend, we discovered that rustup default stable and rustup update stable crash the ghcr.io/despiegk/builder:latest container (~7s silent failure). Also, several skills use GIT_TOKEN for API calls but this variable does not exist in the env_secrets registry or in actual user env files — only FORGEJO_TOKEN exists. The forge_workflow skill (PR #15) also needs minor polish found during dog-fooding.

Goals

  • Add builder container rustup crash to forge_ci Common CI Issues table
  • Add note to build_lib about direct source $HOME/.cargo/env fallback in containers
  • Standardize all skills on FORGEJO_TOKEN (retire GIT_TOKEN references)
  • Polish forge_workflow skill: add duplicate-check step, fix token variable name
  • Update env_secrets to remove ambiguity about token names
## Context During CI setup for freezone backend and frontend, we discovered that `rustup default stable` and `rustup update stable` crash the `ghcr.io/despiegk/builder:latest` container (~7s silent failure). Also, several skills use `GIT_TOKEN` for API calls but this variable does not exist in the env_secrets registry or in actual user env files — only `FORGEJO_TOKEN` exists. The forge_workflow skill (PR #15) also needs minor polish found during dog-fooding. ## Goals - Add builder container rustup crash to `forge_ci` Common CI Issues table - Add note to `build_lib` about direct `source $HOME/.cargo/env` fallback in containers - Standardize all skills on `FORGEJO_TOKEN` (retire `GIT_TOKEN` references) - Polish `forge_workflow` skill: add duplicate-check step, fix token variable name - Update `env_secrets` to remove ambiguity about token names
mik-tf changed title from Document builder container CI gotchas in forge_ci and build_lib skills to Document CI gotchas and standardize FORGEJO_TOKEN across skills 2026-02-17 19:04:20 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
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
geomind_code/dev_docs#16
No description provided.