.rubocop.yml in gitlab-styles-11.0.0 vs .rubocop.yml in gitlab-styles-13.0.0

@@ -1,15 +1,23 @@
 inherit_from:
-  - rubocop-default.yml
+  - rubocop-all.yml
+  - rubocop-minimal.yml
+  - rubocop-internal-affairs.yml
   - .rubocop_todo.yml
 
 require:
   - rubocop/cop/internal_affairs
   - rubocop-rake
 
+inherit_mode:
+  merge:
+    - Exclude
+
 AllCops:
   NewCops: disable # https://gitlab.com/gitlab-org/ruby/gems/gitlab-styles/-/issues/40
+  Exclude:
+    - 'playground/**/*'
 
 Gemspec/DevelopmentDependencies:
   EnforcedStyle: gemspec
   Enabled: true
 
@@ -21,6 +29,25 @@
 # This only makes sense for cops that are included with RuboCop. We could add
 # our own config/default.yml and do something like
 # https://github.com/rubocop/rubocop-rspec/blob/master/lib/rubocop/rspec/inject.rb,
 # but realistically this is OK here.
 InternalAffairs/UndefinedConfig:
+  Enabled: false
+
+# Disable Rails-specific cops auto-enabled as part of `gitlab-styles`.
+CodeReuse/ActiveRecord:
+  Enabled: false
+
+Cop/ActiveRecordDependent:
+  Enabled: false
+
+Cop/ActiveRecordSerialize:
+  Enabled: false
+
+Cop/PolymorphicAssociations:
+  Enabled: false
+
+Cop/RedirectWithStatus:
+  Enabled: false
+
+Cop/InBatches:
   Enabled: false