On-demand config migration PRs using Dashboard

[rarkins]

What would you like Renovate to be able to do?

Add a checkbox to the dependency dashboard which allows users to open a migration PR on demand

If you have any ideas on how this should be implemented, please tell us here.

Remove the log warning display in dashboard (so that this information is not duplicated).

Display the message prominently that config migration is required (maybe with a learn more link).

Have a checkbox allowing users to open the config migration PR.

Not sure what to do if they uncheck the checkbox after the PR is created though. Maybe keep it? They can close it manually if they really want.

Is this a feature you are interested in implementing yourself?

No

[HonkingGoose]

Not sure what to do if they uncheck the checkbox after the PR is created though. Maybe keep it? They can close it manually if they really want.

I think we can keep the default behavior:

1. Select PR via Dependency Dashboard
2. Don't want the PR anymore: close it yourself

If you want to do the "close PR if checkbox is unchecked" thing, there's a possible edgecase:
Renovate de-selects the checkboxes after it finishes the requested run on the repository. So wouldn't Renovate then close the config migration PR on the next run?

[rarkins]

Actually, if we detect that the PR is open we should remove the message and the checkbox from the dashboard (or perhaps replace it with a message/link to the PR)

[HonkingGoose]

I vote "replace it with a message/link to the PR" then.

The Dependency Dashboard should always show all pending stuff, removing the message and checkbox goes against that idea.

[HonkingGoose]

Actually, if we detect that the PR is open we should remove the message and the checkbox from the dashboard (or perhaps replace it with a message/link to the PR)

How about moving the checkbox item to different sections on the Dependency Dashboard? Like this:

1. Renovate detects config migration is needed,
2. Renovate creates a new checkbox for the config migration on the Dependency Dashboard in the Pending approval section,
3. User clicks the config migration checkbox,
4. Renovate creates the PR,
5. Once PR is open: Renovate moves the checkbox to the Open section.

What happens next depends on the user:

• User merges config PR: Renovate drops the checkbox from the Dependency Dashboard -> done.
• User closes config PR: Renovate moves the checkbox to the Ignored or Blocked section -> done.

If user wants new config migration PR, after ignoring one: user renames old PR to something else, and Renovate creates a new PR.

[rarkins]

I think that a migration PR is much more important than regular ones so should be in its own section (at the top) instead of combined with other Pending PRs where it could be missed

[HonkingGoose]

You're right, let's put the config migration in its own section at the top.