summaryrefslogtreecommitdiff
path: root/Guardfile
Commit message (Collapse)AuthorAgeFilesLines
* Add Ruby 3.1 to CI (#558)Peter Goldstein2022-01-271-0/+2
| | | | | | | | | | | | | | | | | | * Add Ruby 3.1 to CI Update Rubocop for recent Rubies Disable Rubocop run for Rubies before Ruby 2.4 Quote '3.0' in the CI configuration to ensure it loads a 3.0.x Ruby Set RUBYOPT="--disable_error_highlight" so Ruby 3.1 error matchers pass * Add CHANGELOG.md entry * Re-add deleted line from CHANGELOG.md * Set minimum supported Ruby version to 2.4. Remove a number of code bits designed to support Rubies below version 2.4 * Bump version. Remove unneeded require from Gemfile. Add require to spec/support file
* Bring integration tests into main test harnessMichael Herold2017-02-031-3/+19
| | | | | | | | | | | | | | | | We have a nice integration spec harness, so let's make sure we use it when we're working on the gem. I'm making the following changes: * Make `bundle exec rake` run integration specs, except on Travis. * Silence a warning in the OmniAuth integration spec that has nothing to do with Hashie. * Make Guard run integration specs when appropriate. Now, when you run all tasks you will run integration specs. Also, if you modify an integration spec, it will run. Lastly, if you modify anything in `lib` the integration specs will run. * Keeps the extra Travis build that only runs integration specs. Travis didn't like the Rake task that included it and there's extra signal by doing it this way anyway.
* Upgraded to RuboCop 0.34.2.dblock2015-10-251-1/+1
|
* Fix: working guard.dB2014-08-241-1/+1
|
* Update Rubocop to 0.25.0 and get it passingMichael Herold2014-08-231-3/+3
|
* Remove reference to singleton_class, that's Ruby 1.9 only.Michael Bleigh2011-08-021-1/+1
|
* Switch to Bundler for gem management and Guard for autotesting.Michael Bleigh2011-07-221-0/+5