Provide possibility to overwrite default onboarding config repository or the config itself

[Ziemnior]

Hi there. In my org we have multiple projects, consisting of multiple repositories and because of this, I do not fancy pasting config in dozens of repositories, when said config does not change across them at all.
I'm not a js/ts guy, so please correct me if I'm wrong:

after Checking if this org/owner has a default Renovate preset which can be used. log is being printed, orgName is being created and then it is being used as a org prefix when building a full path to the renovate-config repository, which I guess is a go-to place for default config. Then, if such repository does not exist in the org, default config is being loaded, with No default org/owner preset found, so the default onboarding config will be used instead. Note: do not be concerned with any 404 messages that preceded this. log.

What I would like to be able to do, is to:

• being able to configure this repository name through config.js (file with list of tracked repos etc) - something that would allow to pass custom repo name in const repo = ` ${orgName}/renovate-config` ; line
• or be able to overwrite the default config is some way, allowing me to point to my default.json config in repository which holds config.js file

I don't know which solution would suit your product better, I'm open to discussion here, as long as I will be able to provide you with any valuable input.

Edit: if you think this would be a added value, I think I will be able to create a PR with configurable repository name.

[viceice]

this will not be configurable.

Checkout docs at https://docs.renovatebot.com/config-presets/

Renovate will do this for onboarding config:

1. check default.json in <org-name>/renovate-config repo
2. check renovate-config.json in <org-name/.` repo
3. use onboardingConfig from config.js

If you're using the hosted github app

1. put your shared preset to a public repo on github, eg myorg/.github/some-file.json
2. put onbording config {"extends": ["github>myorg/.github//some-file"] } to target-org/.github/renovate-config.json

If you self-host

1. put your shared preset to a public repo on github, eg myorg/.{platform}/some-file.json
2. put onbording config {"extends": ["local>myorg/.{platform}//some-file"] } to onboardingConfig

[ankitdadhich]

Also what would be equivalent to extends: ["local>our-org/our-renovate"]

mine config looks like this, but it does not pick default.json
extends: [ "config:base", "local>https://gitlab.myorg.io/path-to-repo/default.json" ],

[viceice]

extends: [ "config:base", "local>path-to-repo" ],

@ankitdadhich search the docs for preset and onboarding for config options

[rarkins]

No https or host name is allowed

[stefan-g]

@viceice i have define a self hosted onboarding config in my config.js. In the logs of the renovate-runner it says that instead of the setting from my config.js, the settings from env config is used. Is there a way to change this default behavior or do i have to remove the RENOVATE_ONBOARDING_CONFIG in the renovate.gitlab-ci.yml file?

[viceice]

env has preference

[github-actions[bot]]

Hi there,

This is intended as a polite, automated request that users avoid @ mentioning repository maintainers like @rarkins or @viceice. Doing so causes annoying mobile notifications and makes it harder to maintain this repository.

We know it might be common elsewhere but we participate in hundreds of discussions a week and would need to turn off GitHub mobile notifications if we were mentioned in every one.

As a general rule, we will read and respond to all discussions in this repository, so there is no need to mention us.

Thanks, the Renovate team