Skip to content

Fix incorrect and outdated instructions in the README - #9

Merged
igray merged 2 commits into
mainfrom
readme-fixes
Aug 1, 2026
Merged

Fix incorrect and outdated instructions in the README#9
igray merged 2 commits into
mainfrom
readme-fixes

Conversation

@igray

@igray igray commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Follow-up to #8. Each item below was verified against the repo or upstream rather than eyeballed.

Incorrect

  • rake spec does not exist. The Rakefile defines test and code_analysis only, so the documented command fails with Don't know how to build task 'spec'. Now bundle exec rake test.
  • The EDITORS.md link 404s. Shopify moved those docs to https://shopify.github.io/ruby-lsp/editors.html, which still documents linters. The other four links in the README were checked and return 200.

Outdated

  • The Ruby 3.0 minimum (raised from 2.5 in 0.4.0) was undocumented.
  • rake code_analysis was undocumented. Worth calling out since CI doesn't run it, so it relies on contributors remembering.
  • The release instructions now mention that pushing the tag triggers the release workflow added in Create GitHub releases automatically on tag push #8.
  • version.rb is given with its full path.

Trivial

  • "they must in your Gemfile" was missing a word.
  • "Ruby::Lsp::Reek" in the Code of Conduct section was bundle gem boilerplate.

The Usage section is deliberately untouched — the linter examples still show [ "rubocop", "reek" ]. RuboCop's rubocop vs rubocop_internal split is upstream's nuance to document, not this gem's.

Verified bundle exec rake test (4 runs, 0 failures) and bundle exec rake code_analysis (0 warnings) both pass, since the README now tells contributors to run them.

🤖 Generated with Claude Code

igray and others added 2 commits August 1, 2026 15:50
- `rake spec` is not a task in this project; the test task is `test`
- The EDITORS.md link 404s, the docs moved to shopify.github.io/ruby-lsp
- Document `rake code_analysis` and the Ruby 3.0 minimum
- Drop `rubocop` from the linter examples, since specifying it now logs a
  RuboCop 1.70 warning unrelated to this addon; explain it below instead
- Note that pushing the tag now creates the GitHub release

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
RuboCop's `rubocop` vs `rubocop_internal` distinction is upstream's to
document, not ours. The examples exist to show how to add reek alongside
the linter most users already run.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@igray
igray merged commit 968feb6 into main Aug 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant