Rubocop: Only disable transactions for some migration helpers

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

We want to make sure that we only disable transactions where necessary (eg concurrent index/FK creation) and that we don't end up mixing normal statements into a migration that runs outside of a transaction scope.

See further and as an example: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24047#note_129120279

Edited Sep 13, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading