A suggested workflow for testing Renovate config changes

[jamietanna]

Hey folks - I know that some of y'all have wondered about different ways to get feedback on your configuration changes, and confirm they're correct.

I've promised for a bit I'll write up how I'm doing that - which I did yesterday.

Take a read and I'd welcome feedback! I'd also like to see what we can do to improve the docs we currently have around this, potentially with a separate page detailing the options we have

(This is in the Contributor Announcements as it's something that folks more engaged with Renovate may be interested in, but this

[reduckted]

You say that you use platform=local, but I've found that doesn't work: #36538

Are you working around that somehow, or is there a specific code path that I'm hitting and you're not?

[jamietanna]

Ah no, it's a little further down the post:

If I'm needing to determine what changes will be made against a repo, I'll end up running Renovate against the repo in non-dry-run mode (the default) which will start processing the repo.

If I need to actually modify the repo - or as you say, test postUpdateOptions or postUpgradeTasks, I'll not use platform=local or --dry-run, and instead actually run against a repo

[reduckted]

Ah, right, that would be the difference then.

Thanks for the write-up. 👍