Upgrade rubocop-capybara to 3.x (#7256) and decide the future of .rubocop.yml
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start by checking PR #7256's CI after its rebase, then read the rubocop-capybara changelog and inspect .rubocop.yml. Run bundle exec rubocop spec/system to verify the plugin loads and identify any needed config changes; compare any failures with the reported Selenium errors. Done means reporting whether the upgrade works and recommending whether the unused RuboCop configuration and plugins should be kept, wired into CI, or removed.
Written by the indexing model from the issue text.
Description
Problem
Dependabot's #7256 bumps rubocop-capybara from 2.23 to 3.1 (a major version). Its last CI run failed ruby_lint and rspec. The lint failure was an unrelated issue that's since been fixed on main, and the PR has been asked to rebase, so the first step is to see what's actually still failing.
Context
rubocop-capybarais in the Gemfile's development/test group and listed underplugins:in.rubocop.yml.- CI does not run it.
ruby_lintrunsbundle exec standardrb, which uses.standard.yml, not.rubocop.yml. So the bump only matters to people who runbundle exec rubocoplocally.
Tasks
- Check #7256's CI after the rebase. If it's green, check locally that
bundle exec rubocop spec/systemstill loads the plugin under 3.x (read the changelog for renamed or removed cops and config keys) and fix.rubocop.ymlif needed - If it's still red, find out whether the failures are caused by the bump or just flaky (system spec Selenium errors)
- Bigger question, for a separate PR: should
.rubocop.ymland its plugins stay at all, given CI only runs Standard? Either wire them intobin/lint/CI or remove the unused gems. Comment with a recommendation.
Difficulty: easy to intermediate.
- Dominant language
- Ruby
- Stars
- 384
- Forks
- 558
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 63
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 rubyforgood/casa
-
⛓️ Security Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rubyforgood/casa#7404 ·
Maintainers usually reply within 1 day
-
Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rubyforgood/casa#7402 ·
Maintainers usually reply within 1 day
-
Remove the bin/bundle binstub (Heroku warns it can break Bundler on deploy)Possibly taken @Akash-Dhanwate claimed this 8 days ago. Opendependencies Difficulty: Easy Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
rubyforgood/casa#7325 · 2 comments ·
Maintainers usually reply within 1 day
-
Reports page: move export-button disable/re-enable into a Stimulus controllerMay be free again @Akash-Dhanwate claimed this 9 days ago, and no pull request is open. OpenDifficulty: Easy Good First Issue Help Wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rubyforgood/casa#7311 · 2 comments ·
Maintainers usually reply within 1 day
-
New case: use Stimulus for the "I don't know the court date yet" toggleMay be free again @Aryankn29 claimed this 9 days ago, and no pull request is open. OpenDifficulty: Easy Good First Issue Help Wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rubyforgood/casa#7310 · 1 comment ·
Maintainers usually reply within 1 day
All issues in rubyforgood/casa
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
internetee/registry#2984 ·
Maintainers usually reply within 6 days
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configuredPossibly taken @mimosa claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
riscv/riscv-unified-db#2829 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
docker-library/ruby#534 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100