file-crdb-issue
Filing GitHub Issues for CockroachDB
File issues on cockroachdb/cockroach using the repo's issue templates and
CockroachDB labeling conventions.
Workflow
Step 1: Discover Issue Templates
The repo has issue templates in .github/ISSUE_TEMPLATE/. Blank issues are
disabled, so one of these templates must be used:
- bug_report.md — Reproducible bugs
- feature_request.md — New functionality proposals
- performance-inquiry.md — Performance problems
For investigation issues (tracking research/analysis work that doesn't fit the above), use the investigation structure in the Investigation section below instead of a template.
More from cockroachdb/cockroach
commit-helper
Help create git commits and PRs with properly formatted messages and release notes following CockroachDB conventions. Use when committing changes or creating pull requests.
501backport-pr-assistant
Help backport PRs to release branches using the backport CLI tool. Use when backporting changes that have merge conflicts requiring manual resolution.
75reduce-unoptimized-query-oracle
Reduce an unoptimized-query-oracle test failure log to the simplest possible reproduction case. Use when you have unoptimized-query-oracle*.log files from a failed roachtest and need to find the minimal SQL to reproduce the bug.
63engflow-artifacts
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.
29table-driven-test
Guidelines for creating clean, well-structured table-driven tests in Go following CockroachDB conventions.
26integration-test
Guidelines for writing integration tests with CockroachDB test servers, including when to use them and how to use sqlutils.
18