Vitali Tatarintev 4f2ac51644 Add Rubocop check to avoid using be_success ... Prevent using `be_success` call in controller specs to avoid getting following deprecation warning: ``` DEPRECATION WARNING: The success? predicate is deprecated and will be removed in Rails 6.0. Please use successful? as provided by Rack::Response::Helpers. ```		2019-08-28 08:43:47 +02:00
..
code_reuse	Link to issue in CodeReuse/ActiveRecord message	2019-05-22 11:37:46 +12:00
gitlab	Utilize RuboCop's Include/Exclude config	2019-08-26 12:24:25 +00:00
graphql	Add a cop to ensure we authorize GraphQL types	2019-06-21 13:00:50 +02:00
migration	Adds cop to enforce string limits on migrations	2019-08-23 21:36:12 +00:00
qa	Change element_with_pattern cop to not use quotes	2019-07-10 16:10:28 -07:00
rspec	Add Rubocop check to avoid using be_success	2019-08-28 08:43:47 +02:00
active_record_association_reload_spec.rb
avoid_break_from_strong_memoize_spec.rb
avoid_return_from_blocks_spec.rb
avoid_route_redirect_leading_slash_spec.rb
destroy_all_spec.rb
group_public_or_visible_to_user_spec.rb
include_action_view_context_spec.rb	Add Rubocop rule to ban include ActionView::Context	2019-04-29 06:14:53 -07:00
include_sidekiq_worker_spec.rb
inject_enterprise_edition_module_spec.rb	Extend cop for verifying injecting of EE modules	2019-07-30 14:52:54 +02:00
line_break_around_conditional_block_spec.rb
prefer_class_methods_over_module_spec.rb
project_path_helper_spec.rb
ruby_interpolation_in_translation_spec.rb
safe_params_spec.rb
sidekiq_options_queue_spec.rb