Updates from rspec-dev that were missed

Author: JonRowe

.github/FUNDING.yml

@@ -0,0 +1,5 @@
+# This file was generated on 2019-12-05T21:32:24+00:00 from the rspec-dev repo.
+# DO NOT modify it by hand as your changes will get lost the next time it is generated.
+
+github: [JonRowe]
+open_collective: rspec

BUILD_DETAIL.md

@@ -1,5 +1,5 @@
 <!---
-This file was generated on 2018-04-17T19:41:57+02:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:32:24+00:00 from the rspec-dev repo.
 DO NOT modify it by hand as your changes will get lost the next time it is generated.
 -->
 
@@ -68,8 +68,8 @@ $ bin/cucumber
 
 ## YARD documentation
 
-RSpec uses [YARD](http://yardoc.org/) for API documentation on the [rspec.info site](http://rspec.info/).
-Our commitment to [SemVer](htp://semver.org) requires that we explicitly
+RSpec uses [YARD](https://yardoc.org/) for API documentation on the [rspec.info site](https://rspec.info/).
+Our commitment to [SemVer](https://semver.org) requires that we explicitly
 declare our public API, and our build uses YARD to ensure that every
 class, module and method has either been labeled `@private` or has at
 least some level of documentation. For new APIs, this forces us to make

CODE_OF_CONDUCT.md

@@ -1,5 +1,5 @@
 <!---
-This file was generated on 2018-04-17T19:41:57+02:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:32:24+00:00 from the rspec-dev repo.
 DO NOT modify it by hand as your changes will get lost the next time it is generated.
 -->
 
@@ -46,14 +46,14 @@ when an individual is representing the project or its community.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported by contacting one of the project maintainers listed at
-http://rspec.info/about/. All complaints will be reviewed and investigated
+https://rspec.info/about/. All complaints will be reviewed and investigated
 and will result in a response that is deemed necessary and appropriate to the
 circumstances. Maintainers are obligated to maintain confidentiality with
 regard to the reporter of an incident.
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 1.3.0, available at
-[http://contributor-covenant.org/version/1/3/0/][version]
+[https://contributor-covenant.org/version/1/3/0/][version]
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/3/0/
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/3/0/

CONTRIBUTING.md

@@ -1,5 +1,5 @@
 <!---
-This file was generated on 2018-04-17T19:41:57+02:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:32:24+00:00 from the rspec-dev repo.
 DO NOT modify it by hand as your changes will get lost the next time it is generated.
 -->
 
@@ -13,8 +13,8 @@ If you'd like to help make RSpec better, here are some ways you can contribute:
   - by running RSpec HEAD to help us catch bugs before new releases
   - by [reporting bugs you encounter](https://github.com/rspec/rspec-support/issues/new) with [report template](#report-template)
   - by [suggesting new features](https://github.com/rspec/rspec-support/issues/new)
-  - by improving RSpec's [Relish](https://relishapp.com/rspec) or [API](http://rspec.info/documentation/) documentation
-  - by improving [RSpec's website](http://rspec.info/) ([source](https://github.com/rspec/rspec.github.io))
+  - by improving RSpec's [Relish](https://relishapp.com/rspec) or [API](https://rspec.info/documentation/) documentation
+  - by improving [RSpec's website](https://rspec.info/) ([source](https://github.com/rspec/rspec.github.io))
   - by taking part in [feature and issue discussions](https://github.com/rspec/rspec-support/issues)
   - by adding a failing test for reproducible [reported bugs](https://github.com/rspec/rspec-support/issues)
   - by reviewing [pull requests](https://github.com/rspec/rspec-support/pulls) and suggesting improvements

DEVELOPMENT.md

@@ -1,12 +1,12 @@
 <!---
-This file was generated on 2018-04-17T19:41:57+02:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:32:24+00:00 from the rspec-dev repo.
 DO NOT modify it by hand as your changes will get lost the next time it is generated.
 -->
 
 # Development Setup
 
 Generally speaking, you only need to clone the project and install
-the dependencies with [Bundler](http://bundler.io/). You can either
+the dependencies with [Bundler](https://bundler.io/). You can either
 get a full RSpec development environment using
 [rspec-dev](https://github.com/rspec/rspec-dev#README) or you can
 set this project up individually.
@@ -22,7 +22,7 @@ Clone the repo:
 $ git clone [email protected]:rspec/rspec-support.git
 ```
 
-Install the dependencies using [Bundler](http://bundler.io/):
+Install the dependencies using [Bundler](https://bundler.io/):
 
 ```
 $ cd rspec-support
@@ -31,7 +31,7 @@ $ bundle install
 
 To minimize boot time and to ensure we don't depend upon any extra dependencies
 loaded by Bundler, our CI builds avoid loading Bundler at runtime
-by using Bundler's [`--standalone option`](http://myronmars.to/n/dev-blog/2012/03/faster-test-boot-times-with-bundler-standalone).
+by using Bundler's [`--standalone option`](https://myronmars.to/n/dev-blog/2012/03/faster-test-boot-times-with-bundler-standalone).
 While not strictly necessary (many/most of our contributors do not do this!),
 if you want to exactly reproduce our CI builds you'll want to do the same:
 
@@ -114,7 +114,7 @@ Here's a short, non-exhaustive checklist of things we typically ask contributors
 
 # Adding Docs
 
-RSpec uses [YARD](http://yardoc.org/) for its API documentation. To
+RSpec uses [YARD](https://yardoc.org/) for its API documentation. To
 ensure the docs render well, we recommend running a YARD server and
 viewing your edits in a browser.
 

REPORT_TEMPLATE.md

@@ -1,5 +1,5 @@
 <!---
-This file was generated on 2018-04-17T19:41:57+02:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:32:24+00:00 from the rspec-dev repo.
 DO NOT modify it by hand as your changes will get lost the next time it is generated.
 -->
 

script/functions.sh

@@ -6,7 +6,7 @@ source $SCRIPT_DIR/travis_functions.sh
 source $SCRIPT_DIR/predicate_functions.sh
 
 # If JRUBY_OPTS isn't set, use these.
-# see http://docs.travis-ci.com/user/ci-environment/
+# see https://docs.travis-ci.com/user/ci-environment/
 export JRUBY_OPTS=${JRUBY_OPTS:-"--server -Xcompile.invokedynamic=false"}
 SPECS_HAVE_RUN_FILE=specs.out
 MAINTENANCE_BRANCH=`cat maintenance-branch`
@@ -187,7 +187,10 @@ function run_all_spec_suites {
   fold "rspec-core specs" run_spec_suite_for "rspec-core"
   fold "rspec-expectations specs" run_spec_suite_for "rspec-expectations"
   fold "rspec-mocks specs" run_spec_suite_for "rspec-mocks"
-  fold "rspec-rails specs" run_spec_suite_for "rspec-rails"
+
+  if rspec_rails_compatible; then
+    fold "rspec-rails specs" run_spec_suite_for "rspec-rails"
+  fi
 
   if rspec_support_compatible; then
     fold "rspec-support specs" run_spec_suite_for "rspec-support"

script/predicate_functions.sh

@@ -65,6 +65,14 @@ function is_ruby_23_plus {
   fi
 }
 
+function rspec_rails_compatible {
+  if is_ruby_23_plus; then
+    return 0
+  else
+    return 1
+  fi
+}
+
 function rspec_support_compatible {
   if [ "$MAINTENANCE_BRANCH" != "2-99-maintenance" ] && [ "$MAINTENANCE_BRANCH" != "2-14-maintenance" ]; then
     return 0

script/update_rubygems_and_install_bundler

@@ -6,8 +6,8 @@ set -e
 source script/functions.sh
 
 if is_ruby_23_plus; then
-  gem update --system
-  gem install bundler
+  yes | gem update --system
+  yes | gem install bundler
 else
   echo "Warning installing older versions of Rubygems / Bundler"
   gem update --system '2.7.8'