feat: interactive reconfigure pr

[RahulGautamSingh]

Changes

• check if reconfigure pr exists
• if reconfigure pr found, add a comment on the pr with expected pr's list and config description
• expand reconfigure cache to store extraction result so we can skip processing the reconfigure branch if it has not changed
• make slight changes mergeRenovateConfig fn such that it can pass the branchName to the detectConfigFile fn which comes in handy when trying to read the config file from reconfigure branch using api endpoint
• added tests

Context

• Closes: Interactive Reconfigure PR #547

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required (todo)

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

1. reconf pr Rahul-renovate-testing/recon-pr#1
2. Reconfigure PR Rahul-renovate-testing/repro-10869-new#6

[secustor]

has conflicts else LGTM

[RahulGautamSingh]

This has been approved for a while. Needs attention :)

[renovate-release]

🎉 This PR is included in version 40.57.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 40.57.0

Your semantic-release bot 📦🚀

[ben-foxmoore]

Is there any documentation associated with this change which describes how to use the feature? Eager to try it out, but it's not clear how to trigger it. Does the PR need to be named something specific? Will it detect simply based on the renovate file changing? Does any configuration change need to be made to enable the feature?

[RahulGautamSingh]

Is there any documentation associated with this change which describes how to use the feature? Eager to try it out, but it's not clear how to trigger it. Does the PR need to be named something specific? Will it detect simply based on the renovate file changing? Does any configuration change need to be made to enable the feature?

This section here is dedicated to reconfigration. It needs an update though, I will do it soon.

For you case:

1. Create a new renovate/reconfigure branch
2. Make edits to the renovate.json file as per your needs
3. Create a PR using that branch
4. Run renovate locally (if self-hosted) or wait for hosted Renovate app to add a comment to your PR explaining the expected outcome from the new config.

Any feedback which helps you understand the changes better, are welcome. Thanks!

Answer to you question

Does the PR need to be named something specific?
No.

Will it detect simply based on the renovate file changing?
Yes.

Does any configuration change need to be made to enable the feature?
No.

[LecrisUT]

Is it already live?

[rarkins]

@LecrisUT at the time you asked, this merge was 15 minutes old so Renovate hadn't even completed publishing a new version yet.

Then assuming you are referring to the Mend-hosted app, it never goes immediately live. Upgrades are done typically twice a week and monitored.

[ben-foxmoore]

Is there any documentation associated with this change which describes how to use the feature? Eager to try it out, but it's not clear how to trigger it. Does the PR need to be named something specific? Will it detect simply based on the renovate file changing? Does any configuration change need to be made to enable the feature?

This section here is dedicated to reconfigration. It needs an update though, I will do it soon.

For you case:

1. Create a new renovate/reconfigure branch
2. Make edits to the renovate.json file as per your needs
3. Create a PR using that branch
4. Run renovate locally (if self-hosted) or wait for hosted Renovate app to add a comment to your PR explaining the expected outcome from the new config.

Any feedback which helps you understand the changes better, are welcome. Thanks!

Answer to you question

Perfect, thanks @RahulGautamSingh! Something like that would be immensely useful in the docs I suspect 😉