You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs/usermanuals/en/reference/yaml-templates.md: broken example — 'Materialise any of them with: forgelm quickstart <template-name> --output config.yaml', followed by --dry-run and then training. (DOC-D3B04A-008) #222
A user who only wants to inspect and adapt the template triggers a model download and a full GPU training run, then a chat session, before the documented dry-run step.
Primary finding
DOC-D3B04A-008 — docs/usermanuals/en/reference/yaml-templates.md: broken example — 'Materialise any of them with: forgelm quickstart <template-name> --output config.yaml', followed by --dry-run and then training.
The document says. 'Materialise any of them with: forgelm quickstart <template-name> --output config.yaml', followed by --dry-run and then training.
What the code does. Without --dry-run, forgelm quickstart TEMPLATE generates the config, immediately starts training in a subprocess, and then launches forgelm chat. Only --dry-run stops after generating the config.
User impact. A user who only wants to inspect and adapt the template triggers a model download and a full GPU training run, then a chat session, before the documented dry-run step.
Proposed correction.shell $ forgelm quickstart <template-name> --output config.yaml --dry-run # generate only $ forgelm --config config.yaml --dry-run $ forgelm --config config.yaml and add: "Without --dry-run, forgelm quickstart starts training right away and then opens forgelm chat (skip chat with --no-chat)."
Turkish mirror. the Turkish page has the same error; fix both in the same PR
Acceptance criteria
Each statement is re-checked against the code at fix time.
Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
Every finding in this issue is resolved or explicitly closed with a reason.
Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.
Activity