README.md in octokit-4.18.0 vs README.md in octokit-4.19.0
- old
+ new
@@ -649,11 +649,11 @@
This will install project dependencies and get you up and running. If you want
to run a Ruby console to poke on Octokit, you can crank one up with:
script/console
-Using the scripts in `./scripts` instead of `bundle exec rspec`, `bundle
+Using the scripts in `./script` instead of `bundle exec rspec`, `bundle
console`, etc. ensures your dependencies are up-to-date.
### Code of Conduct
We want both the Octokit.rb and larger Octokit communities to be an open
@@ -711,20 +711,16 @@
[bootstrapping]: http://wynnnetherland.com/linked/2013012801/bootstrapping-consistency
[VCR]: https://github.com/vcr/vcr
## Supported Ruby Versions
-This library aims to support and is [tested against][travis] the following Ruby
+This library aims to support and is [tested against][actions] the following Ruby
implementations:
-* Ruby 2.0
-* Ruby 2.1
-* Ruby 2.2
-* Ruby 2.3
-* Ruby 2.4
* Ruby 2.5
* Ruby 2.6
+* Ruby 2.7
If something doesn't work on one of these Ruby versions, it's a bug.
This library may inadvertently work (or seem to work) on other Ruby
implementations, but support will only be provided for the versions listed
@@ -735,10 +731,10 @@
run and pass on that implementation. When something breaks on your
implementation, you will be responsible for providing patches in a timely
fashion. If critical issues for a particular implementation exist at the time
of a major release, support for that Ruby version may be dropped.
-[travis]: https://travis-ci.org/octokit/octokit.rb
+[actions]: https://github.com/octokit/octokit.rb/actions
## Versioning
This library aims to adhere to [Semantic Versioning 2.0.0][semver]. Violations
of this scheme should be reported as bugs. Specifically, if a minor or patch