Updated common plaintext files (from rspec-dev) [ci skip]

Author: JonRowe

.github/FUNDING.yml

@@ -1,5 +1,4 @@
-# This file was generated on 2019-11-27T18:54:20+00:00 from the rspec-dev repo.
+# This file was generated on 2019-12-05T21:25:47+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 2015-12-07T22:01:06+11:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:25:47+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](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
+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
 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 2015-12-07T22:01:06+11:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:25:47+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
-https://rspec.info/about/. All complaints will be reviewed and investigated
+http://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
-[https://contributor-covenant.org/version/1/3/0/][version]
+[http://contributor-covenant.org/version/1/3/0/][version]
 
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/3/0/
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/3/0/

CONTRIBUTING.md

@@ -1,5 +1,5 @@
 <!---
-This file was generated on 2015-12-07T22:01:06+11:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:25:47+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.
 -->
 
@@ -11,10 +11,10 @@ We welcome contributions from *everyone*. While contributing, please follow the
 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-rails/issues/new?template=bug_report.md)
-  - by [suggesting new features](https://github.com/rspec/rspec-rails/issues/new?template=feature_request.md)
-  - 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 [reporting bugs you encounter](https://github.com/rspec/rspec-rails/issues/new) with [report template](#report-template)
+  - by [suggesting new features](https://github.com/rspec/rspec-rails/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 taking part in [feature and issue discussions](https://github.com/rspec/rspec-rails/issues)
   - by adding a failing test for reproducible [reported bugs](https://github.com/rspec/rspec-rails/issues)
   - by reviewing [pull requests](https://github.com/rspec/rspec-rails/pulls) and suggesting improvements
@@ -24,47 +24,21 @@ If you need help getting started, check out the [DEVELOPMENT](DEVELOPMENT.md) fi
 
 Thanks for helping us make RSpec better!
 
-## Rspec issues labels definition
+## `Small` issues
 
-### `Your first PR` issues
+These issue are ones that we be believe are best suited for new contributors to
+get started with. They represent a meaningful contribution to the project that
+should not be too hard to pull off.
 
-These issues are the ones that we be believe are best suited for new
-contributors to get started on. They represent a potential meaningful
-contribution to the project that should not be too hard to pull off.
+## Report template
 
-### `Needs reproduction case` issues
-
-These issues are ones that have been labelled by the maintainers that we
-believe do not currently have enough information to be reproduced the RSpec
-team. While not directly counted by the GitHub contribution graph, we consider
-helping us to reproduce the issue with a repro case as an extremely meaningful
-contribution.
-
-### `Has reproduction case` issues
-
-These issues are the ones that have reproduction cases, able to start working on
-immediately. These are good ones to tackle to help us actively fix bugs.
+Having a way to reproduce your issue will be very helpful for others to help confirm,
+investigate and ultimately fix your issue. You can do this by providing an executable
+test case. To make this process easier, we have prepared one basic
+[bug report templates](REPORT_TEMPLATE.md) for you to use as a starting point.
 
 ## Maintenance branches
 
 Maintenance branches are how we manage the different supported point releases
 of RSpec. As such, while they might look like good candidates to merge into
 master, please do not open pull requests to merge them.
-
-## How do the cukes work?
-
-The cucumber features for RSpec rails document how it works, but are also quasi
-executable tests for the framework. They execute in the context of a pre-setup
-Rails app.
-
-1. Before the cucumber specs run, the directory `tmp/aruba` is cleared
-2. If the example app hasn't already been created,
-   `bundle exec rake generate:app generate:stuff` is executed.
-3. The example app is copied in to `tmp/aruba`
-4. Everything in `tmp/aruba/spec/*` is deleted apart from `spec/spec_helper.rb` and
-   `spec/rails_helper.rb`
-5. the cucumber suite executes, creating files in that app and executing them
-
-The best way to debug the app is to run a failing cucumber feature, which will
-leave the test files intact in `tmp/aruba`, then you can cd in to that director
-and run it in the bundle context of the aruba app.

DEVELOPMENT.md

@@ -1,12 +1,12 @@
 <!---
-This file was generated on 2015-12-07T22:01:06+11:00 from the rspec-dev repo.
+This file was generated on 2019-12-05T21:25:47+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](https://bundler.io/). You can either
+the dependencies with [Bundler](http://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-rails.git
 ```
 
-Install the dependencies using [Bundler](https://bundler.io/):
+Install the dependencies using [Bundler](http://bundler.io/):
 
 ```
 $ cd rspec-rails
@@ -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`](https://myronmars.to/n/dev-blog/2012/03/faster-test-boot-times-with-bundler-standalone).
+by using Bundler's [`--standalone option`](http://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](https://yardoc.org/) for its API documentation. To
+RSpec uses [YARD](http://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.
 

ISSUE_TEMPLATE.md

@@ -0,0 +1,24 @@
+### Subject of the issue
+<!---
+Describe your issue here.
+-->
+
+### Your environment
+* Ruby version:
+* rspec-rails version:
+
+### Steps to reproduce
+<!---
+Tell us how to reproduce this issue. Please provide a working demo, you can use
+this [templates](REPORT_TEMPLATE.md) as a base.
+-->
+
+### Expected behavior
+<!---
+Tell us what should happen.
+-->
+
+### Actual behavior
+<!---
+Tell us what happens instead.
+-->

REPORT_TEMPLATE.md

@@ -0,0 +1,43 @@
+<!---
+This file was generated on 2019-12-05T21:25:47+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.
+-->
+
+# Report template
+
+```ruby
+# frozen_string_literal: true
+
+begin
+  require "bundler/inline"
+rescue LoadError => e
+  $stderr.puts "Bundler version 1.10 or later is required. Please update your Bundler"
+  raise e
+end
+
+gemfile(true) do
+  source "https://rubygems.org"
+
+  gem "rspec", "3.7.0" # Activate the gem and version you are reporting the issue against.
+end
+
+puts "Ruby version is: #{RUBY_VERSION}"
+require 'rspec/autorun'
+
+RSpec.describe 'additions' do
+  it 'returns 2' do
+    expect(1 + 1).to eq(2)
+  end
+
+  it 'returns 1' do
+    expect(3 - 1).to eq(-1)
+  end
+end
+```
+
+Simply copy the content of the appropriate template into a `.rb` file on your computer
+and make the necessary changes to demonstrate the issue. You can execute it by running
+`ruby rspec_report.rb` in your terminal.
+
+You can then share your executable test case as a [gist](https://gist.github.com), or
+simply paste the content into the issue description.