Preset for the org/user should not overwrite a defined onboardingConfig #29923
Squazz
started this conversation in
Suggest an Idea
Replies: 1 comment 2 replies
-
We are not using a cached version of the onboardingConfig. If we find a preset for the org/user we add it to the onboardingConfig thinking that the configuration user/org wants during onboarding will be included in that preset. renovate/lib/workers/repository/onboarding/branch/config.ts Lines 80 to 91 in 522ce15 If you think that's an issue/inconsistent then you can change this discussion to a Suggest an Idea and reframe your question. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
bitbucket server, 37.420.1
Please tell us more about your question or problem
I'm testing out how to configure the onboardingConfig
I've updated the onboardingConfig property in the config file that I'm handing to my container when running Renovate. And the debug log tells me that it got the updated onboardingConfig.
But for some reason, it seems to always fall back to a cached version of the onboardingConfig.
Where does this cache come from?
Is there some way I can tell it to not use the cache?
Can I somehow prune the cache?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions