Allow Dry Run Per Project
Gr33nbl00d opened this issue · comments
Whenever adding renovate to a new project i usually have to do some exclusions and config adoptions per project.
It would be nice to have some kind of dry run per project.
The idea is that you could add dryRun:true to your project level renovate config.
And than an issue is created with a list of changes.
This way it would be easy to adopt the config as long as it takes till renovate does exactly what it should do
Hi @Gr33nbl00d, thanks for opening a feature request.
I think I found a similar feature request in the repository at renovatebot/renovate#547.
Copy/paste from top post of renovatebot/renovate#547:
Consider the case when someone has already activated Renovate but wants to make a configuration change. My idea:
They create an issue "Reconfigure Renovate".
Renovate bot looks for this each run
If found, it opens a "Reconfigure Renovate" PR to close that issue.
PR is initially "empty" but user can edit renovate.json in branch and see results just like the onboarding PR.Essentially, it's an interactive way to update renovate configuration and helps them validate the config.
I'll let the Renovate team decide on the priority of this feature request, and if this is a duplicate of renovatebot/renovate#547 or not.
Is the idea of this request to be that you add dryRun=true to your renovate.json and merge it and then check the logs to make sure it's going to do what you want?
BTW in the meantime you may find setting dependencyDashbordApproval=true useful as then it won't create any new branches/PRs either - just the issue
This is more or less the idea, but i would like to be able to view the information in some other way not in the logs (by mail or as an issue or something like this). Because not all developers in our company have access to the logs.
I will give dependencyDashbordApproval a try
There's no point in a dry run if you can't view the logs, so in that case the recommendation is definitely dependencyDashbordApproval