rust-lang / rust-lang/rust-clippy
Integrate with hound?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Hound is an open source service repo that thoughtbot runs. After enabling it on your repo, when a pull request is opened, hound analyzes it and comments on the diff if it finds problems. This lets PR submitters fix those issues before the code gets merged into master.
There's a section in hound's CONTRIBUTING.md about the current linters they offer and how to add a new linter.
Each linter service has its own repo, for example, houndci/swift, which manages the service that calls out to the specific linter, in this case SwiftLint. It looks like the code that interfaces a service with Hound is mostly in, in this case, lib/swift_lint.
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.
Research direction
Start with Hound's CONTRIBUTING.md linter section and the linked houndci/swift/lib/swift_lint example to understand the integration pattern. Locate the Rust Clippy service entry point, which this issue does not name, and define the integration scope; done means Hound can analyze Clippy changes and report findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100