Allow ignorePresets to be propagated throuh nested presets

[secustor]

Tell us more.

Currently ignorePresets has to be in the same config as the extends which introduces the preset which should be ignored.

In case of centrally managed presets that can become an issue.
e.g. a the repo config extends config:best-practices but at the same time via organizational preset e.g. a replacement should be ignored.

[rarkins]

Can you give more details of an example setup?

[rarkins]

That's a tough one because the repo config is resolved first

[secustor]

Never said it is easy 😅
I simply wanted to discuss if this is something we should support.

[rarkins]

I think not - we need to process in the order that presets are resolved

[Finkregh]

I just ran into the same issue, my employer is providing a central renovate which uses config:recommended which includes :ignoreModulesAndTests, which I'd like to ignore as i.e. /tests/requirements.txt should be still be updated.

We (org level) mostly have centrally managed renovate configs ourselves, which I guessed would allow ignorePresets, but it seems that only works when it is applied in each repo's own config.

Is there any way to override the ignorePaths via a central config which is loaded via extends?

[Finkregh]

using ignorePaths directly instead of ignorePresets behaves the same; works in repo's own config, not in one loaded via extends :(