Skip to content

Don't require class documentation in background migrations anymore

What does this MR do and why?

Don't require class documentation in background migrations anymore

This Rubocop rule was added in b3331cf3 . It is ignored a lot but now that we have db/docs/batched_background_migrations this is also redundant because we already have to document the background migration in the YML file. We don't want to duplicate this effort so we can remove this rule.

$ git grep 'disable Style/Documentation' |wc -l
      65

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Dylan Griffith

Merge request reports