Feedback and contributions

Questions about the instructions, missing examples, and reports of broken behaviour help improve Forge. Use the existing GitHub issue forms; you will need a GitHub account to submit an issue or propose an edit.

What you want to report	Where to go
Incorrect instructions or a missing user guide	Documentation feedback
CLI installation, prompts, options, or diagnostics	create-forge issues
Generated code, notebooks, dependencies, or CI	forge-template issues
A new project type or capability	Template feature request
A correction to the template repository's own docs	Template documentation feedback

If you are unsure which repository owns a problem, open an issue in create-forge and describe what you were trying to do. Maintainers can route it. Search existing issues first so related reports stay together.

For documentation, include the page URL, the unclear or incorrect step, and what you expected to find. Suggested wording is welcome but optional. For bugs, include a minimal command, your versions and operating system, and the relevant error. Remove credentials and private project data.

Suggest an edit

Every guide has a source-edit link and a documentation-feedback link. Small wording fixes can go directly into a pull request. New guides should explain the use case, show runnable commands, describe expected output, and give readers their next useful action.

Follow the contribution guide for the repository you are changing:

• create-forge contributing
• forge-template contributing

Security reports

Use the repository's private reporting process for suspected vulnerabilities; do not put them in public issues:

• create-forge security policy
• forge-template security policy

---

Missing an example or found an unclear step? Send documentation feedback.