Make sure we're not using EE classes in migrations
We need to avoid issues like #32790 (closed) where we're using EE classes in db/post_migrate
.
If all migrations should go to FOSS, all migration tests should go to FOSS.
This can be done by Rubocop to check that if the class set in MIGRATION
is an EE class (the source is under ee/
), it should contain EE guard (return unless Gitlab.ee?
) in the up
and down
(if not no-op) methods.
Edited by Lin Jen-Shin