3 comments (3 comments)0 reactions (0 reactions)2 assignees (2 assignees)Go40,090 stars (40,090 stars)6,186 forks (6,186 forks)batch import
good first issuehelp wantedtype/enhancement
Description
This issue does not include a description.
Contributor guide
- Tech stack
- go
- Domain
- toolingdeveloper experience
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- half day
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Basic Gogolangci lint knowledgeTiDB repository access
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 30
- Research direction
- The issue requests enabling the sqlclosecheck linter in golangci lint for TiDB. First, locate the .golangci.yml configuration file in the repository root. Then, add 'sqlclosecheck' to the list of enabled linters under the 'linters' section. Run 'golangci lint run' to verify no new warnings. Check comments for any known issues. Since assignees exist, verify if there is progress on a branch.