feat(migrate): migrate nested configuration files #5986
Merged
Conversation
This file contains hidden or 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
ematipico
force-pushed
the
feat/multiple-migrations
branch
2 times, most recently
from
16c3975 to
b9be0f8
Compare
Conaclos
approved these changes
May 12, 2025
Member
|
Nice work :) |
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.
Summary
Part of #2228
This PR adds a new feature to the
migratecommand. With this PR, the command is now able to migrate nested configuration files.We take advantage of the light scanner to return the path to he configuration files. This will fix some repositories in the ecosystem CI, where they have nested
biome.jsoninside their repositories, but the command fails because it sees old configuration files.This is also part of the monorepo support.
Test Plan
Added a new test