The standardrb rake task is now run in CI against Ruby 2.7. Adds a .rubocop.yml for better integration with the Ruby LSP.
Also:
updates the circleci config to use the latest Ruby orb
leverages the built-in bundle install command so we don't have to manage the circleci cache ourselves
adds Gemfile.lock and gemfiles/*.lock to version control for better caching in CI and per the bundler docs recommendation
Q: Should I commit my Gemfile.lock when writing a gem?
A: Yes, you should commit it. The presence of a Gemfile.lock in a gem’s repository ensures that a fresh checkout of the repository uses the exact same set of dependencies every time. We believe this makes repositories more friendly towards new and existing contributors. Ideally, anyone should be able to clone the repo, run bundle install, and have passing tests. If you don’t check in your Gemfile.lock, new contributors can get different versions of your dependencies, and run into failing tests that they don’t know how to fix.
The
standardrbrake task is now run in CI against Ruby 2.7. Adds a .rubocop.yml for better integration with the Ruby LSP.Also: