aboutsummaryrefslogtreecommitdiffstats
path: root/guides/bug_report_templates/generic_gem.rb
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Merge pull request #34421 from ↵Ryuta Kamizono2018-11-111-1/+1
| | | | | | | albertoalmagro/use-assert-not-instead-of-refute" This reverts commit ab5d5c95ec51c63d58d7e75694af748f165e2228, reversing changes made to ef4f5ef69b5a50c897bbb17f6b36b729dff12e6c.
* Prefer assert_not instead of refute [ci skip]Alberto Almagro2018-11-101-1/+1
| | | | | | | | As mentioned in the contributing to Ruby on Rails guides, we should prefer `assert_not` instead of `refute`. And the best place to start giving example are our bug report templates.. See: https://github.com/rails/rails/blame/master/guides/source/contributing_to_ruby_on_rails.md#L256
* Update bug report templatesRobin Dupret2018-10-281-9/+1
| | | | | | | | | | Given that Bundler 1.10 was released back in 2015, we can assume that people are at least on this version or a higher one so there is no need to ask people to upgrade. Also, given that Rails 5.0 supports Ruby 2.2+ and given that this version come with Minitest 5.4.3 bundled, we don't need to ensure backward compatibility with Minitest 4.
* use "minitest" consistentlyXavier Noria2018-09-111-1/+1
| | | | | | | | | The name of the minitest library is spelled that way: regular font, and lowercase. Lowercase is used even at the beginning of sentences, see http://docs.seattlerb.org/minitest/ I double-checked this with @zenspider too (thanks!).
* Update bug report templatesbogdanvlviv2018-04-101-1/+1
| | | | Set Rails 5.2.0 in templates
* Update bug report templatesbogdanvlviv2018-02-171-1/+2
| | | | | | Prepare bug report templates for Rails 6.0 development Add missing `require "active_support"` in `guides/bug_report_templates/generic_gem.rb`
* Add newlines before/after the `git_source` in bug report templatesRyuta Kamizono2017-09-271-0/+2
| | | | [ci skip]
* Change :github git source for bug report templatesbogdanvlviv2017-09-271-0/+1
| | | | | | | :github source uses `git://` url by default, `https://` is recommended. See http://bundler.io/v1.15/guides/git.html#security We do the same in our `Gemfile` and templates.
* Use frozen string literal in guides/Koichi ITO2017-08-131-0/+2
|
* Revert "Merge pull request #29540 from kirs/rubocop-frozen-string"Matthew Draper2017-07-021-1/+0
| | | | | This reverts commit 3420a14590c0e6915d8b6c242887f74adb4120f9, reversing changes made to afb66a5a598ce4ac74ad84b125a5abf046dcf5aa.
* Enforce frozen string in RubocopKir Shatrov2017-07-011-0/+1
|
* Update the Gem Bug Report Templates to 5.1.0Alex Kitchens2017-05-011-1/+1
| | | | 5.1.0 has been released, and the gem templates can reflect that now.
* Update bug report templatesMatthew Draper2017-03-221-1/+1
|
* Bump bug report template versions to 5.0.1Daniel Martin2017-01-261-1/+1
|
* applies new string literal convention in guidesXavier Noria2016-08-061-6/+6
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Bump version for master bug report templatesJon Moss2016-07-051-1/+1
|
* Update Ruby report templatesRafael Mendonça França2016-05-101-1/+1
|
* Output an error message and raise an error if bundler 1.10.x is not ↵akihiro172015-06-061-1/+6
| | | | installed when reporting bugs
* Add the bug report templates to the Travis CI buildRoque Pinel2015-06-051-3/+8
| | | | | | | | | | | | The bug report templates are now executed from the `ci/travis.rb` when `GEM` contains `guides`. I started by creating a `test` task in `guides/Rakefile` to handle this, but since inline `gemfile` must not be executed with `bundle exec`, that rake task would not be consistent with others. So I went back by executing them directly from `Build`. Use inline Gemfile dependency when reporting gem bugs
* Add a "generic" bug report templateGodfrey Chan2015-04-191-0/+15
This template gives contributors a starting point to use when reporting bugs that does not involve Active Record or Action Pack.