Shared issue forms and security reporting guidance for Caffeine projects.
- Bug report: unexpected behavior, including regressions.
- Feature request: a problem or use case and the desired outcome.
- Other issue: documentation, maintenance, and usage questions.
The forms live in .github/ISSUE_TEMPLATE. Blank issues
are disabled; Other issue provides a lightweight fallback. The chooser also links
to the security reporting policy.
This repository must remain public. Once these files are on its default branch,
GitHub uses them for Caffeine repositories without their own issue templates or
chooser configuration. A repository with valid templates or configuration in its
own .github/ISSUE_TEMPLATE directory overrides the entire shared set; GitHub
does not merge the two directories.
To customize a project's forms, copy the shared set into that project and edit it there. That copy will need to be maintained separately. See GitHub's default community file documentation.
The forms do not assign labels, issue types, projects, or maintainers. If adding labels later, create them in every repository that uses the forms.
Keep required fields limited to information needed to act on a report. Use runtime-neutral wording and free-text versions so the forms work across Bun, Node.js, Deno, browsers, and other environments.
After changes reach the default branch, check the issue chooser and forms in a repository that inherits them. Confirm their order, required fields, and security link without submitting a test issue. Private vulnerability reporting must be enabled on each affected repository; these files do not enable it.