Skip to content

Conversation

@Ayush2k02
Copy link

@Ayush2k02 Ayush2k02 commented Dec 25, 2025

Fixes #185

This PR adds comprehensive GitHub issue templates to improve the quality and consistency of bug reports and feature requests for the @neondatabase/serverless package.

Added three files to .github/ISSUE_TEMPLATE/:

1. bug_report.yml - Bug Report Template

Comprehensive form with fields for:

  • Bug description - Clear description of the issue
  • Reproduction steps - Step-by-step guide to reproduce
  • Expected vs Actual behavior - What should happen vs what actually happens
  • Code sample - Minimal reproducible code with TypeScript syntax highlighting
  • Runtime environment - Dropdown for Node.js, Cloudflare Workers, Vercel Edge, Deno, Bun, Browser, etc.
  • Version information - Package version, Node.js version, TypeScript version
  • Environment details - OS, framework, deployment platform
  • Error logs - Stack traces and error messages with shell formatting
  • Additional context - Screenshots, related issues, etc.

2. feature_request.yml - Feature Request Template

Structured form with fields for:

  • Problem statement - What problem does this solve?
  • Proposed solution - Detailed description of the feature
  • Alternatives considered - Other approaches explored
  • Use case - Real-world scenario for the feature
  • Example API - Optional code showing desired usage
  • Additional context - Supporting materials

3. config.yml - Issue Template Configuration

Provides helpful links:

  • Neon Documentation
  • Neon Discord Community
  • Neon Support

Also allows blank issues for edge cases.

Example

When users click "New Issue", they'll see:

  • Bug Report option
  • Feature Request option
  • Open a blank issue option

These templates will be active once merged. You can preview them in the GitHub UI by:

  1. Going to the repository
  2. Clicking "Issues" → "New Issue"
  3. Seeing the template selection screen

Fixes neondatabase#185

Added comprehensive issue templates to improve bug reporting and
feature request quality. This will help maintainers quickly understand
and triage issues.

Changes:
- Created bug_report.yml with detailed fields for:
  - Bug description and reproduction steps
  - Expected vs actual behavior
  - Code samples with syntax highlighting
  - Runtime environment selection (Node.js, Workers, Edge, etc.)
  - Package and environment versions
  - Error logs and stack traces

- Created feature_request.yml with fields for:
  - Problem description and motivation
  - Proposed solution
  - Alternative approaches considered
  - Use case explanation
  - Example API usage

- Added config.yml with helpful links to:
  - Neon documentation
  - Discord community
  - Support resources

Benefits:
- Structured bug reports with all necessary information
- Easier for maintainers to reproduce and fix issues
- Better feature request clarity and context
- Reduced back-and-forth for missing information
- Links to appropriate resources for common questions
@Ayush2k02 Ayush2k02 marked this pull request as draft December 25, 2025 04:58
@Ayush2k02 Ayush2k02 marked this pull request as ready for review December 25, 2025 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bugs Template

1 participant