whitesmith / whitesmith/rubycritic
To standardrb or not to standardrb?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3.5k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
It seems like "everyone" is picking up standardrb as their linter of choice. Should Rubycritic follow the herd?
One possible advantage is that standardrb's set of selected cops is sufficiently safe and tested that we could potentially put standardrb --fix in a GitHub action that auto-commits any fixes.
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 by reviewing Rubycritic’s current linting setup and comparing it with standardrb, which is the proposed replacement. Determine whether adopting standardrb and an auto-fixing GitHub Action is appropriate; done means the project has a decided linting approach and any required configuration or workflow changes are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100