| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
- Followup of https://github.com/rails/rails/pull/20929.
[ci skip]
|
| |
|
|
| |
this will silence deprecation warnings
|
| |
|
|
| |
installed when reporting bugs
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
With Bundler `1.10.3`, it is possible to list the gems inline without the
need to create a `Gemfile` if none is found in the current directory.
|
| |
|
|
|
| |
This template gives contributors a starting point to use when reporting bugs
that does not involve Active Record or Action Pack.
|
| |
|
|
| |
[ci skip]
|
| |
|
|
|
|
|
| |
- 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.
|
| |
|
|
|
|
|
|
| |
- 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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- `secrets.secret_token` is now used in all places `config.secret_token` was
- `secrets.secret_token`, when not present in `config/secrets.yml`,
now falls back to the value of `config.secret_token`
- when `secrets.secret_token` is set, it over-writes
`config.secret_token` so they are the same (for backwards-compatibility)
- Update docs to reference app.secrets in all places
- Remove references to `config.secret_token`, `config.secret_key_base`
- Warn that missing secret_key_base is deprecated
- Add tests for secret_token, key_generator, and message_verifier
- the legacy key generator is used with the message verifier when
secrets.secret_key_base is blank and secret_token is set
- app.key_generator raises when neither secrets.secret_key_base nor
secret_token are set
- app.env_config raises when neither secrets.secret_key_base nor
secret_token are set
- Add changelog
Run focused tests via
ruby -w -Itest test/application/configuration_test.rb -n '/secret_|key_/'
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This reverts commit fd6d7835.
We are back on arel master, see b395265f.
|
| |
|
|
|
|
| |
We should rely instead on the version supported by Active Record
Closes #14809
|
| |
|
|
|
|
|
|
| |
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]
|
| | |
|
| |
|
|
|
|
| |
renamed to `Minitest`
Ref: https://github.com/seattlerb/minitest/blob/master/History.txt
|
| |
|
|
|
|
|
|
|
|
| |
[ci skip].
This solves:
```
Could not find gem 'arel (~> 5.0.0) ruby', which is required by gem 'rails (>= 0) ruby', in any of the sources.
```
|
| |
|
|
|
|
| |
[ci skip]
Fixes #12848.
|
| | |
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[ci skip]
|
| |
|
|
|
|
| |
* use `Minitest::Test` instead of deprectaed `MiniTest::Unit::TestCase`
[ci skip]
|
| | |
|
| | |
|
| |
|
|
| |
since users just copy and paste and the class name is never changed
|
| | |
|
|
|
This commit closes issue #9775.
|
