Clean up existing Clippy warnings before enabling Clippy CI
@officialfrancismendoza is already working on this.
Since Jul 16, 2026.
Assessment
This issue has not been assessed yet.
Description
The repository currently produces a substantial number of warnings and errors when running:
cargo clippy --workspace --all-targets --all-features
Before Clippy can be enabled as a required pull-request check, the existing findings should be reviewed and resolved or explicitly allowed where appropriate.
Once the workspace reaches a clean baseline, add a dedicated GitHub Actions workflow that runs Clippy independently from build, test, formatting, and documentation checks.
Clippy is specifically a linting tool for finding common mistakes and improving Rust code, but enforcing it only makes sense after the repository has a clean baseline.
- Dominant language
- Rust
- Stars
- 25
- Forks
- 18
- Avg merge
- 16h 38m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bcgit/bc-rust
-
good first issue refactor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100