Autoclose existing PRs when repo is disabled

[rarkins]

What would you like Renovate to be able to do?

Have the option to "clean up" existing PRs when a repo is skipped or disabled for either reason:

• enabled=false in config, or
• it's a fork without forkProcessing=true

There may be other cases where INFO: Repository is disabled - skipping is true to cover, but not all of them. For example if the repo is archived then we can't make any changes.

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

Introduce a new option pruneBranchesWhenDisabled which defaults to false. The reason to make this opt-in is that it will introduce extra work each run which is not necessary. It would instead be reserved for "cleanup" situations such as caused by #21237

Ideally if the repo cache is in use then we can also save the fact we've already done a cleanup and then not do it the next time we run on the repo, assuming it's still disabled.

Is this a feature you are interested in implementing yourself?

No

[rarkins]

Steps to reproduce the first example (enabled=false):

• Create a new repo with .nvmrc and empty renovate.json
• Let Renovate create a PR to update Node.js
• Set enabled=false in the renovate.json
• Re-run Renovate and observe it skips the repo but leaves the PR open

[renovate-release]

🎉 This issue has been resolved in version 35.31.0 🎉

The release is available on:

• GitHub release
• 35.31.0

Your semantic-release bot 📦🚀