aboutsummaryrefslogtreecommitdiffstats
path: root/guides/bug_report_templates/active_record_gem.rb
Commit message (Collapse)AuthorAgeFilesLines
* Specify sqlite gem version explicitly in version-specific bug report templatesSergey Ponomarev2019-02-041-1/+1
|
* 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/+1
| | | | | | 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-9/+9
| | | | | 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-2/+9
| | | | | | | | | | | | 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
* Use force: true options for creating tables in bug templatesPrathamesh Sonpatki2015-01-191-2/+2
| | | | | | | - Generally we have to run the bug templates multiple times to get them right and it always complains because the posts and comments tables already exist due to earlier runs. - Using force: true will eliminate this issue.
* Update bug report templates to use version 4.2.0 instead of 5.0.0 [ci skip]Prathamesh Sonpatki2015-01-041-1/+1
| | | | | | | | - Right now master is 5.0.0. Latest gem release is 4.2.0 for which we are accepting bug reports. So lets use it in bug report templates. - 5.0.0 is not installable as it's not available on Rubygems yet. So the gem bug templates are not usable without editing the version. Using 4.2.0 will make them usable again.
* Using Rails 5.0 in bug report templates [ci skip]Lucas Caton2015-01-021-1/+1
|
* Ensure backward compatibility between Minitest 5 and 4Robin Dupret2013-12-271-0/+3
| | | | | | | | Define Minitest::Test in case we are running the gist under Minitest 4 and avoid relying on MiniTest::Unit::TestCase to avoid displaying warning on version five. [ci skip]
* Minitest::Unit::TestCase is Minitest::Test [ci skip]Arun Agrawal2013-12-261-1/+1
|
* Change all `MiniTest` to `Minitest` since, `MiniTest` namespace has been ↵Vipul A M2013-12-181-1/+1
| | | | | | renamed to `Minitest` Ref: https://github.com/seattlerb/minitest/blob/master/History.txt
* Use MiniTest::Unit::TestCase instead of Minitest::TestRobin Dupret2013-09-071-1/+1
| | | | | | | Since Rails 4.0.x is depending on Minitest 4.x, the constant won't be available so the gist won't run. [ci skip]
* Updated bug report templatesPaul Nikitochkin2013-08-211-1/+1
| | | | | | * use `Minitest::Test` instead of deprectaed `MiniTest::Unit::TestCase` [ci skip]
* Use activerecord 4.0.0 for reporting bugs using the template[ci skip]Prathamesh Sonpatki2013-06-271-1/+1
|
* bump the rails version in bug report templateNeeraj Singh2013-04-171-1/+1
|
* template should have generic nameNeeraj Singh2013-04-041-1/+1
| | | | since users just copy and paste and the class name is never changed
* write sql queries to terminalNeeraj Singh2013-04-021-1/+3
|
* gist for Active Record issues [Neeraj Singh & Xavier Noria]Xavier Noria2013-04-011-0/+35
This commit closes issue #9775.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-28 09:27:37 +0000