Loading page
About this tool
Create GitHub issue form YAML for bug reports, feature requests and support questions with validated fields and labels.
This tool generates GitHub issue form YAML — the structured template format stored in .github/ISSUE_TEMPLATE/ that replaces free-text issues with validated fields like dropdowns, required textareas and checkboxes. It follows GitHub's documented issue-forms schema (name, description and body are mandatory; validations.required enforces a field). Maintainers get bug reports with reproduction steps and versions attached instead of one-line complaints.
Open GitHub Issue Template Generator on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
Emits the exact top-level keys and body item types (markdown, input, textarea, dropdown, checkboxes) GitHub's issue-forms parser accepts.
Marks critical fields with validations.required so the issue cannot be submitted without them.
Bug report, feature request and support question with sensible labels, title prefixes and field sets you can adjust.
Issue templates are plain Markdown files that pre-fill the issue body and can be edited or deleted by the reporter; issue forms are YAML files that render as a web form with typed fields and required-field validation. Forms use the .yml extension in .github/ISSUE_TEMPLATE/ and currently work on public repositories, while Markdown templates work everywhere.
In the .github/ISSUE_TEMPLATE/ directory of the default branch, one .yml or .yaml file per template — for example .github/ISSUE_TEMPLATE/bug_report.yml. An optional config.yml in the same folder can disable blank issues and add contact links to external support channels.
Add a validations block with required: true to the body item, which blocks submission until the field is filled. For checkboxes, set required: true on the individual option instead — that is how 'I searched for duplicates' confirmations are enforced.
Five body types: markdown (static guidance text), input (single line), textarea (multi-line, optionally rendered as code with the render attribute), dropdown (single or multiple choice) and checkboxes. Every type except markdown needs an attributes.label, and ids let automation read specific answers later.