Autocorrect RuboCop offenses in migrations #15155
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Frontend
eduardoj
force-pushed
the
refactoring/rubocop_safe_autocorrections_migrations
branch
4 times, most recently
from
62792e9
to
4937f27
Compare
... RuboCop offenses in migrations
... RuboCop offense in migrations
... in migrations
... to also work with linters changes
eduardoj
force-pushed
the
refactoring/rubocop_safe_autocorrections_migrations
branch
from
4937f27
to
96be64f
Compare
danidoni
approved these changes
Nov 3, 2023
eduardoj
deleted the
refactoring/rubocop_safe_autocorrections_migrations
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I grouped the fixes for RuboCop offenses for migrations and data migrations.
The "Isolated Migrations" GitHub action was adapted to not complain when there are also changes in the linters configuration.