Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: HonkingGoose <[email protected]>
  • Loading branch information
RahulGautamSingh and HonkingGoose authored Oct 9, 2024
1 parent 9cf67ca commit d2b3427
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/usage/config-migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Using the latest names:
- helps you find the documentation for the config

Renovate can create a config migration Pull Request, to migrate legacy config in your configuration file.
To get automated config migration pull requests from Renovate: set the [`configMigration`](./configuration-options.md#configmigration) config option to `true`.
To get automated config migration Pull Requests from Renovate: set the [`configMigration`](./configuration-options.md#configmigration) config option to `true`.

Config migration PRs are disabled by default.
But we recommend you enable config migration PRs, because:
Expand All @@ -44,12 +44,12 @@ Renovate takes no action.
Renovate will:

1. Create a Config Migration PR
1. If the Dependency Dashboard issue is enabled then Renovate puts a link to the Config Migration PR on the dashboard
1. If the Dependency Dashboard issue is enabled, then Renovate puts a link to the Config Migration PR on the dashboard

### Config migration needed, but disabled

If config migration is needed, but disabled then Renovate adds a checkbox to the Dependency Dashboard (if the dashboard exists).
This is known as "on-demand" config migration because migration PRs are only created at the request of the user by ticking the checkbox.
This is known as "on-demand" config migration, because migration PRs are only created at the request of the user by ticking the checkbox.

The checkbox looks like this:

Expand Down

0 comments on commit d2b3427

Please sign in to comment.