1 comment (1 comment)0 reactions (0 reactions)0 assignees (0 assignees)Rust1,587 stars (1,587 stars)28 forks (28 forks)user submission
help wanted
Description
🤔 Similar to https://github.com/vercel/turborepo/issues/178
Contributor guide
- Tech stack
- rust
- Domain
- clideveloper experiencetooling
- 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.
- needs investigation
- Prerequisites
- Rust basicsHTTP client (reqwest)Semantic versioning
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 35
- Research direction
- First, review the linked turborepo issue (#178) to understand the expected behavior. Then, explore the current codebase (e.g., src/main.rs or similar) to identify where to add an update check. Consider using reqwest for HTTP and semver for version comparison. Implementation should be non blocking (async if possible). Finally, document the new feature in README.