CONTRIBUTING.md in link-header-parser-4.0.0 vs CONTRIBUTING.md in link-header-parser-5.0.0

- old
+ new

@@ -6,13 +6,13 @@ 1. Review open [pull requests][pulls]. 1. Report a new [issue][issues]. _Only do this after you've made sure the behavior or problem you're observing isn't already documented in an open issue._ ## Getting Started -link-header-parser-ruby is developed using Ruby 2.6.9 and is additionally tested against Ruby 2.7, 3.0, and 3.1 using [GitHub Actions](https://github.com/jgarber623/link-header-parser-ruby/actions). +link-header-parser-ruby is developed using Ruby 2.7.6 and is additionally tested against Ruby 3.0 and 3.1 using [GitHub Actions](https://github.com/jgarber623/link-header-parser-ruby/actions). -Before making changes to link-header-parser-ruby, you'll want to install Ruby 2.6.9. It's recommended that you use a Ruby version managment tool like [rbenv](https://github.com/rbenv/rbenv), [chruby](https://github.com/postmodern/chruby), or [rvm](https://github.com/rvm/rvm). Once you've installed Ruby 2.6.9 using your method of choice, install the project's gems by running: +Before making changes to link-header-parser-ruby, you'll want to install Ruby 2.7.6. It's recommended that you use a Ruby version managment tool like [rbenv](https://github.com/rbenv/rbenv), [chruby](https://github.com/postmodern/chruby), or [rvm](https://github.com/rvm/rvm). Once you've installed Ruby 2.7.6 using your method of choice, install the project's gems by running: ```sh bundle install ``` @@ -20,10 +20,10 @@ 1. Fork and clone the project's repo. 1. Install development dependencies as outlined above. 1. Create a feature branch for the code changes you're looking to make: `git checkout -b my-new-feature`. 1. _Write some code!_ -1. If your changes would benefit from testing, add the necessary tests and verify everything passes by running `bin/ci`. +1. If your changes would benefit from testing, add the necessary tests and verify everything passes by running `bundle exec rspec`. 1. Commit your changes: `git commit -am 'Add some new feature or fix some issue'`. _(See [this excellent article](https://chris.beams.io/posts/git-commit/) for tips on writing useful Git commit messages.)_ 1. Push the branch to your fork: `git push -u origin my-new-feature`. 1. Create a new [pull request][pulls] and we'll review your changes. ## Code Style