TiDB · pingcap/tidb

Decides from local git changes whether make bazel_prepare must run in TiDB before build or test commands, and reports the evidence for the decision.

pingcap/tidb

Investigates TiDB plan or test-result diffs that the change does not explain, ruling out failpoint setup and merge effects before expected outputs are updated.

pingcap/tidb

Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.

pingcap/tidb

Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.

pingcap/tidb

Use when running tests under tests/realtikvtest that require a local TiUP playground lifecycle with strict startup, readiness checks, and cleanup.

pingcap/tidb

Checks a fix proposed by a user or reviewer for intent, correctness and compatibility before the agent implements it in the TiDB codebase.

pingcap/tidb

Keeps TiDB GitHub issues consistent by following the issue templates, writing reproducible reports, checking for duplicates and applying labels explicitly.

pingcap/tidb

Creates and edits TiDB pull request titles and descriptions without breaking the PR template, and diagnoses bot labels that stay on because of template changes.

pingcap/tidb

Chooses how much validation a TiDB change needs: scoped checks while iterating, required checks at delivery, and expensive runs only when explicitly needed.

pingcap/tidb