4D GitHub CI Setup
1. Generate and copy the CI files
python "$SKILL_DIR/scripts/install_ci.py" --project /path/to/4d-project
install_ci.py generates workflows and may omit the full DLTK build block from
release.yml (product-line, version, build, token) when
secrets.DLTK is absent or still a placeholder in config.yml. Secret values
are never printed.
2. Push Actions secrets (optional)
python "$SKILL_DIR/scripts/set_secrets.py" --project /path/to/4d-project
# or target explicitly:
python "$SKILL_DIR/scripts/set_secrets.py" --repo OWNER/REPO
If config.yml has no secrets section (or no DLTK), skip this step.
Security — do not read the config
- Never read, open, or print
assets/config.yml. It holds the DLTK token. Only the scripts read it; the secret only ever moves throughghvia stdin.config.ymlis git-ignored. - Do not echo the DLTK value, pass it as a CLI argument, or place it in a commit, workflow file, or chat message.
Notes
$SKILL_DIRis this skill's directory: for instance~/.claude/skills/4d-github-ci.- Edit
funding:in config.yml to change the funding handle for all future projects (supports github, patreon, open_collective, ko_fi, custom, ...).