Skip to content

docs: add GitHub issue templates for bug reports and feature requests#45

Merged
gordonmurray merged 1 commit intolance-format:mainfrom
gordonmurray:docs/issue-templates
Apr 7, 2026
Merged

docs: add GitHub issue templates for bug reports and feature requests#45
gordonmurray merged 1 commit intolance-format:mainfrom
gordonmurray:docs/issue-templates

Conversation

@gordonmurray
Copy link
Copy Markdown
Collaborator

Fixes #44

Adds two YAML issue forms under .github/ISSUE_TEMPLATE/:

bug_report.yml

Structured bug report with required fields for:

  • Container tag (dropdown of published tags plus "built locally" and "other")
  • Host OS
  • What happened / expected behavior
  • Reproduction steps (shell-rendered)

Plus optional fields for Lance data source (what wrote the files) and logs/error output.

The container tag dropdown is the main DX win: triage no longer needs to ask "which version are you running" as a first reply, which is currently the most common first question on bug reports in this project.

feature_request.yml

Structured feature request with:

  • Summary (required)
  • Use case (required)
  • Proposed approach (optional)
  • A required checkbox confirming the filer has read the design constraints in CONTRIBUTING.md

The constraint checkbox links to CONTRIBUTING.md (merged in #43) and lists the five load-bearing constraints inline in the description, so the filer sees them even without clicking through.

Notes

Both templates are YAML issue forms, not Markdown. The difference matters: YAML forms enforce required fields at submit time, whereas Markdown templates let users delete the placeholder and file an empty issue.

blank_issues_enabled is left at the default (true) so users can still file unstructured issues if neither template fits. If that turns out to be noisy in practice, a config.yml can be added later to disable blank issues.

Adds two YAML issue forms under `.github/ISSUE_TEMPLATE/`:

- `bug_report.yml` with a required dropdown for the container tag, plus
  required fields for host OS, reproduction steps, and error output. The
  container tag dropdown means triage no longer has to ask "which version
  are you running" as a first reply.
- `feature_request.yml` with summary, use case, optional implementation
  sketch, and a required checkbox confirming the filer has read the design
  constraints in CONTRIBUTING.md.

YAML issue forms enforce required fields at submit time, unlike Markdown
templates where users can delete the placeholders.

Fixes lance-format#44
@gordonmurray gordonmurray merged commit 13da569 into lance-format:main Apr 7, 2026
12 checks passed
@gordonmurray gordonmurray deleted the docs/issue-templates branch April 7, 2026 20:32
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.

docs: add GitHub issue templates for bug reports and feature requests

1 participant