GitHub Issue Template Generator
Live preview, copy or download, free and private.
Loading tool...
What is GitHub Issue Template Generator?
The GitHub Issue Template Generator builds the files GitHub uses to pre-fill new issues. It outputs both formats repositories rely on: a classic Markdown template with YAML front matter (name, about, title, labels, assignees) and a structured Issue Forms YAML file whose input, textarea, dropdown, and checkbox fields are rendered as real form controls. Everything is generated in your browser from a visual editor, with a live preview of the exact file you will commit.
Key Benefits
- Templates load correctly on the first try - front matter and YAML syntax are always valid
- Structured forms with required fields cut back-and-forth on incomplete bug reports
- Consistent titles, labels, and sections make issues searchable and triage-friendly
- No YAML memorization - the field builder handles ids, types, options, and escaping
- Free, private, and offline: nothing is uploaded and no GitHub login is required
Common Use Cases
- •Standardizing bug reports for an open-source project with repro steps and environment fields
- •Collecting feature requests with priority dropdowns and acceptance-criteria textareas
- •Onboarding new maintainers with ready-made templates instead of documentation
- •Cleaning up a repo where issues arrive without versions, logs, or expected behavior
- •Prototyping an issue form layout before committing it to .github/ISSUE_TEMPLATE
How to Use the GitHub Issue Template Generator
- Pick a template kind: Choose between a classic Markdown template (works in every repository) or a structured Issue Forms YAML file with typed fields.
- Fill in the metadata: Set the template name, description, default issue title prefix, labels, and assignees. Lists are converted into valid YAML arrays automatically.
- Build the fields or body: For Issue Forms, add input, textarea, dropdown, and checkbox fields with ids, labels, and required flags. For Markdown, edit the body directly or load the bug-report sample.
- Copy into your repository: Review the live preview, then copy or download the file and save it under .github/ISSUE_TEMPLATE/ in your repository. GitHub picks it up immediately.
Key Features
- Two modes: classic Markdown template and structured Issue Forms YAML.
- Visual field builder for input, textarea, dropdown, and checkbox fields.
- Automatic YAML quoting and escaping for names, labels, and options.
- Labels and assignees lists formatted into valid YAML arrays.
- One-click copy or download as bug_report.md / bug_report.yml, fully in-browser.
Frequently Asked Questions
Where do I put the generated template file?
Commit it under .github/ISSUE_TEMPLATE/ in the default branch of your repository, e.g. .github/ISSUE_TEMPLATE/bug_report.md or bug_report.yml. GitHub starts offering it in the issue picker as soon as the file lands on the default branch.
What is the difference between a Markdown template and Issue Forms?
A Markdown template pre-fills the issue body as free-form text anyone can edit. Issue Forms (YAML, only supported on GitHub.com public repos and private repos with the feature enabled) render structured controls - inputs, dropdowns, checkboxes - and can enforce required fields, so reports arrive complete and consistent.
Why do some values in the YAML appear quoted?
Values that start with special characters (like brackets or #), contain ": " sequences, or would otherwise parse as another YAML type are quoted automatically so the file stays valid. It is cosmetic - GitHub reads both forms the same way.
Can I add multiple templates to one repository?
Yes. Add one file per template in .github/ISSUE_TEMPLATE/, each with its own name and description. Users choose between them when opening an issue. You can also add a config.yml with blank_issues_enabled and contact links to control the chooser.