Elaboration on requireconfig and onboardingconfig

[DesNotMe]

Tell us more.

I have read the docs but I still don't understand the difference between requireconfig and onboardingconfig. I want have a repo that contains my gitlab-ci.yml that runs a pipeline targeting other repos. I want to implement this on other repositories but renovate will always create a basic renovate.json. I want to customise so that other repositories will have the renovate.json I have below, without doing anything manual. This is my current gitlab-ci.yml file in a different repo

`include:

• project: 'renovate-bot/renovate-runner'
  file: '/templates/renovate.gitlab-ci.yml'

renovate:
rules:
- if: '$CI_PIPELINE_SOURCE == "schedule"'
- if: '$CI_PIPELINE_SOURCE == "push"'
variables:
SECRET_KEY_BASE: $SECRET_KEY_BASE
RENOVATE_TOKEN: $SETTINGS__GITLAB_ACCESS_TOKEN
RENOVATE_EXTRA_FLAGS: "--autodiscover=false --platform=gitlab --token=$SETTINGS__GITLAB_ACCESS_TOKEN"
script:
- renovate $REPO_TARGET
tags:
- runner`

this is my ideal renovate.json that I want to add:

{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": [ "config:recommended" ], "labels": ["renovate"], "dependencyDashboard": true, "dependencyDashboardApproval": true, "dependencyDashboardOSVVulnerabilitySummary": "all", "osvVulnerabilityAlerts": true, "vulnerabilityAlerts": { "groupName": null, "enabled": true, "schedule": [], "dependencyDashboardApproval": false, "minimumReleaseAge": null, "rangeStrategy": "update-lockfile", "commitMessageSuffix": "[SECURITY]", "branchTopic": "{{{datasource}}}-{{{depNameSanitized}}}-vulnerability", "prCreation": "immediate", "vulnerabilityFixStrategy": "highest" }, "kubernetes":{ "fileMatch": ["\\.yml"] } }

[rarkins]

I think you should take a step back and reconsider what you say you want. If each repo has the above renovate.json, then the moment you change your mind about any of it, or want to add to it, then you have a big challenge. You'd be better to do this:

• Define a central shared preset for all repos to share (can be in the same repo as you run Renovate from)
• Put that preset in your onboardingConfig/renovate.json instead
• If in future you want to change all repo behavior, you just need to change one file

See https://docs.renovatebot.com/key-concepts/presets/

[DesNotMe]

Thanks @rarkins, apologies for the misconfusion, I'll look into it first.

[DesNotMe]

I tried this I already But every new repo I scanned, will create a new renovate.json , and I will have to add an extra line of code.
"gitlab>ORG_NAME/security-program/renovate-bot:default"

[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