Dillon Welch

Appears to be broken. Not sure if it's a ruby or a mongoid issue. See https://github.com/devise-security/devise-security/runs/4220285439?check_suite_focus=true

If ruby-head is failing the build, it should not stop a PR from being merged. Instead, we should get a notification from a nightly build and/or a build after merging...

https://github.com/devise-security/devise-security/security/code-scanning use the one directly from here https://github.com/marketplace/actions/brakeman-linter seems like the most used one. https://github.com/marketplace/actions/brakeman-action and https://github.com/marketplace/actions/code-review-using-brakeman are other options.

https://github.com/rails/rails/blob/main/.github/workflows/rubocop.yml https://github.com/marketplace/actions/run-rubocop-with-reviewdog is another option https://github.com/devise-security/devise-security/security/code-scanning there is an option listed here This should also update the Rubocop config to account for the cops we want to keep from CodeClimate

You can do the following in `devise` https://github.com/heartcombo/devise#getting-started ``` $ rails generate devise user Running via Spring preloader in process 90483 invoke active_record create db/migrate/20210326055734_devise_create_users.rb create app/models/user.rb invoke test_unit create...

https://github.com/devise-security/devise-security/pull/444 so that we don't run into this issue again.

See https://github.com/devise-security/devise-security/pull/79#discussion_r626276986

The following translation file ```json { "test": { "10": "a", "2": "a" } } ``` will fail no matter which order you put the keys in. Both options output a...