GitHub issue evidence template
Before opening a vague GitHub issue, prepare the evidence maintainers need.
For JS/Vite failures, a useful issue needs more than "it broke." Serious Builder Pro is built around the evidence that AI tools, teammates, and maintainers usually ask for first.
Request accessNo payment is collected yet. This CTA source is the GitHub issue evidence page.
Before and after
Before
"My Vite project fails on build. Any ideas?"
After
"Here is the exact command, versions, first and final error lines, relevant config, reproduction status, redaction note, and the specific maintainer question."
Evidence jobs this page points to
- Reproduction steps or a clear note that no minimal reproduction exists yet.
- Environment and version context.
- Logs and stack traces with useful boundaries.
- Relevant config files or excerpts.
- AI-ready summary that does not invent facts.
Not included
- No issue submission service.
- No private debugging or private log review.
- No maintainer response guarantee.